- This topic has 8 replies, 3 voices, and was last updated 16 years ago by
.
-
Posts
-
I’m having a hard time figuring out why this problem can’t be solved in a forthright manner.
When I start MyEclipse 7.1.1 (the problem has existed in all versions of 7.x) with -clean in myeclipse.ini I get this IClasspathEntry must be abosolute. When this happens, I can’t access many of my projects.
Two [unsatisfactory] remedies have been offered.
1) Create a new workspace and import all projects into it. This works, but the next time I stop and restart MyEclipse, it appears again and I have to do the new workspace, reimport again.
2) I was also told to take -clean out of myeclipse.ini. This also works but appears to disable the feature that prompts for workspace on startup (even though the check box for this is checked) and always puts me in an old workspace requiring me to click File -> Switch Workspace.None of the tech staff has even been able to say where this IClasspathEntry exists and how I could change the absolute value to stop this problem.
I’m using 2) above now, but this is a problem that ought to be able to be solved. I SEE NO LESS THAN 9 ENTRIES when doing a site search for IClasspathEntry. I know I’m not the only one having this problem and I’d really like to see a solution posted.
it looks like changing to Java 6 (1.6.0_10 or later) to run MyEclipse looks like it resolved the issue — we were never able to reproduce it internally but are attempting to fix it by changing the default JRE running MyEclipse in the 7.5 release to 1.6.0_13 — the latest Java 6 release. You might want to give that a try locally to see if it corrects the issue.
https://www.genuitec.com/forums/topic/iclasspathentry-error-when-starting-myeclipse/#post-293414
It seems to me you ought to change MyEclipse to continue to work properly with Java 5. There are tons of people who must user previous versions of the JDK for various reasons. Many government agencies are slow to approve Java upgrades. Some hosting sites are also slow to support newer versions until they’re certain they blow the entire site and all subscribers. They often have to do months of testing before supporting an upgrade.
Pleas ask your programming staff to work on being compatible with Java 5, not forcing upgrade to Java 6 just so a bug in MyEclipse will stop showing up.
@support-nipun wrote:
it looks like changing to Java 6 (1.6.0_10 or later) to run MyEclipse looks like it resolved the issue — we were never able to reproduce it internally but are attempting to fix it by changing the default JRE running MyEclipse in the 7.5 release to 1.6.0_13 — the latest Java 6 release. You might want to give that a try locally to see if it corrects the issue.
https://www.genuitec.com/forums/topic/iclasspathentry-error-when-starting-myeclipse/#post-293414
It seems to me you ought to change MyEclipse to continue to work properly with Java 5. There are tons of people who must user previous versions of the JDK for various reasons. Many government agencies are slow to approve Java upgrades. Some hosting sites are also slow to support newer versions until they’re certain they blow the entire site and all subscribers. They often have to do months of testing before supporting an upgrade.
Please ask your programming staff to work on being compatible with Java 5, not forcing upgrade to Java 6 just so a bug in MyEclipse will stop showing up.
Douglas,
Moving to Java 6 only changes the runtime that runs MyEclipse — it doesn’t effect what Java JDK/JRE you choose to use for your projects.
You could easily setup a new project, with compiler settings of JDK 1.1 and a JRE of 1.1 set on the build path for a new project if you want — JDK 1.6.0_13 is just what will be running MyEclipse 7.5 itself.
Ok, so let me ask you this. I bring up MyEclipse (in my case, Workspaces/MyEclipse 7.1.1). It gives me the IClassPath Error. I then say switch workspaces to Workspaces/MyEclipse 7.1.1 (same as the one I originally brought it up under) and Voila! The problem disappears.
You’ll probably say I should be thankful for this, but I don’t like having to basically boot MyEclipse twice to get it to work.
Very strange… sounds like the ICP issue is coming from the platform on startup — one thing you could try, if you do edit the myeclipse.ini file in your install dir, and remove the “-clean” argument, and restart MyEclipse a few times, does the problem go away?
-clean wipes out the info cache and re-creates it on startup, we added it to fix an error with the workbench not prompting for your workspace on startup, but if that’s not an issue for you, it might do what you want.
When I do that, remove -clean, I don’t get the IClassPath error, but as you say it also doesn’t prompt me for my workspace even though that box is checked to do so under Window > Preferences > General > Startup and Shutdown.
At work, with -clean gone, it boots into the wrong workspace and I have to switch to the correct workspace. At home it boots into the correct workspace, probably because it’s the only workspace I have there, but still gives the IClassPath error and I have to reboot into the same workspace.
This morning, with -clean left in, I had to do the change workspace reboot twice for it to come up correctly (without the iClassPath error).
Weird… but not wonderful!
Interesting… but not amusing!
