- This topic has 13 replies, 4 voices, and was last updated 18 years, 4 months ago by
.
-
Posts
-
I’ll attempt to ask 2 questions here
1. I have set up a number of MyEclipse projects for the team to use.
They work fine, except for one thing. When they are first imported
by a new developer, some JSP files (there’s no pattern to this)
show compilation “errors” (in quotes, because they are not truly errors).
They claim some things cannot be resolved. But if I highlight the
entire contents of the JSP file, cut them, save, then paste them back
in, and save, all the errors disappear.This also sometimes happens when I start MyEclipse. Any ideas?
2. Somehow (it doesn’t matter which JSP editor I use) I can no longer
use F3 to go to a method definition, and links don’t appear when hovering
over an item while pressing Ctrl (I checked the appropriate settings,
they haven’t changed; and it works in Java source).Before we address either can you post the result of MyEclipse > About MyEclipse > Installation Summary for me?
I’ve had similar symptoms.
I think errors may be genuine, to begin with, but the error indications (or some of them) remain, even after the errors have been corrected. For example, the editor may not be able to resolve a bean. Corrections to the other JSPs, that import this JSP, and that define the bean, seems to correct the error in the imported JSP. The error indication in the project browser is removed but the error still shows up in the editor. Usually, shutting down the editor and relaunching it, on the imported JSP, clears the problem.
*** Date: Fri Aug 04 09:32:15 NZST 2006
*** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.5.0_07*** MyEclipse details:
MyEclipse Enterprise WorkbenchVersion: 5.0 Milestone 2
Build id: 20060703-5.0-M2*** Eclipse details:
Eclipse SDKVersion: 3.2.1
Build id: M20060726-0800Eclipse Platform
Version: 3.2.1.r321_v20060705-WMxOFUabkkSGI6x
Build id: M20060726-0800Eclipse RCP
Version: 3.2.0.v20060609m-QtHY09DAsaYSLVj
Build id: M20060726-0800Eclipse Java Development Tools
Version: 3.2.1.r321_v20060705-V29IdJvl4ZbmoD-
Build id: M20060726-0800Eclipse Plug-in Development Environment
Version: 3.2.0.v20060609m——6zXJJzK1Oq
Build id: M20060726-0800Eclipse Project SDK
Version: 3.2.0.v20060609m-fxeEnjYguZnLgQD
Build id: M20060726-0800Eclipse Graphical Editing Framework
Version: 3.2.0.v20060626
Build id: 20060627-0816Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-launcher
C:\tools\eclipse321\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
db8_4c
-vm
C:\WINDOWS\system32\javaw.exesofistek,
I’m assuming that’s an integration or nightly build of Eclipse, we haven’t tested with it so I can’t help too much there.I would point out that we are aware of an issue with new projects where the build cycle will start off before the libraries for the projects are done mounting, and this causes problems with the initial build. The issues are all corrected if a subsequent Project > Clean cycle is fired off.
Does this occur for you guys?
Yes, it is an eclipse integration build – I had issues with the eclipse debugger, which this seems to have fixed. However, the problems with JSF occurred before and after installing this build.
The problems I’ve seen are not always corrected by a clean build of the project. And sometimes the error indication in the editor will be for an earlier error.
Tony
*** Date: Thu Aug 03 23:01:02 EDT 2006
*** System properties:
OS=Windows2000
OS version=5.0
Java version=1.4.2_04*** MyEclipse details:
MyEclipse Enterprise WorkbenchVersion: 4.1.1 GA
Build id: 20060228-4.1.1-GA*** Eclipse details:
Eclipse PlatformVersion: 3.1.0
Build id: I20050401-1645Eclipse Platform
Version: 3.1.0
Build id: I20050401-1645Eclipse Java Development Tools
Version: 3.1.0
Build id: I20050401-1645Eclipse Plug-in Development Environment
Version: 3.1.0
Build id: I20050401-1645Eclipse Project SDK
Version: 3.1.0
Build id: I20050401-1645Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-launcher
C:\eclipse31\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
13a4_74
-data
d:\dev
-vm
c:\j2sdk1.4.2_04\bin\javaw.exeI think sofistek’s problem is different. As I pointed out, these are not errors, as clearing
the file’s contents and then pasting the exact same contents back clears the errors.debedb,
I don’t think that is the final release of 3.1.0, but regardless, my first suggestion would be to upgrade to Eclipse 3.2 SDK GA releasae and MyEclipse 5.0 GA release on August 6th when we release to see if the problem has been resolved.@support-rkalla wrote:
debedb,
I don’t think that is the final release of 3.1.0, but regardless, my first suggestion would be to upgrade to Eclipse 3.2 SDK GA releasae and MyEclipse 5.0 GA release on August 6th when we release to see if the problem has been resolved.I recently downloaded and installed the 5.0My Eclipse GA release, and I noticed that hyperlinks still do not appear when you hover over embedded Java code and hold down the control key.
Did you reinstall a clean version of Eclipse 3.2 SDK from the eclipse.org site as well and install *both* of the applications into new directories and not ontop of the existing ones? Also did you restart using the -clean command line argument when opening your existing workspace?
@support-rkalla wrote:
Did you reinstall a clean version of Eclipse 3.2 SDK from the eclipse.org site as well and install *both* of the applications into new directories and not ontop of the existing ones? Also did you restart using the -clean command line argument when opening your existing workspace?
I had done all of those things, but to no avail. I’ve only ever seen ctrl-hover-links work properly while conducting the recent JSP breakpoint test I did in my test workspace at C:\tempworkspace. I’m starting to wonder if the implementation of my employer’s JSPs is such that the pages do not get parsed properly by the editor/designer in order to properly recognize the embedded Java code scriptlets in the JSP page.
That is most likely what is happening, unfortunately the only indiciation that path parsing and location parsing is not working, is that hovers don’t work. There is no other indication to speak of that would suggest why it’s not working.
You might make sure that it’s a web project, MyEclipse relies heavily on the WebRoot dir to resolve paths and has a problem with paths starting with a slash / (absolute)
