- This topic has 1 reply, 2 voices, and was last updated 21 years ago by
Riyad Kalla.
-
AuthorPosts
-
binyanMemberThis eclipse issue https://bugs.eclipse.org/bugs/show_bug.cgi?id=58607 and the associated ME issue
https://www.genuitec.com/forums/topic/error-creating-ejb-s-and-servlets-closed/
has resulted in a fix that is required on a plugin basis. The following comment from the eclipse issue should shed some light:——- Additional Comment #13 From Dirk Baeumer 2004-04-19 16:47 ——-
OK, here are some explanations:
– Eclipse provides the ability that other plug-in can implement their own
classpath container. This is what MyEclipse does.
– the bogus JUNIT_HOME path variable is caused by a plug-in provided by
Eclipse. We will fix this for the next integration build (I20040420).
– this will not fix the problem with the bogus path provided by MyEclipse. So
to get this working some code has to be changed in MyEclipse.Does the clarify some things ?
————————————————————————————-
The Junit classpath variables and the ME classpath variables had preceeding slashes. Apparently there was a defect in how the junit plugin defined its classpath container. The Junit code was changed from
JavaCore.setClasspathVariable(JUnitPlugin.JUNIT_HOME, new Path(local.getFile()), null);
to
String fullPath= new File(local.getPath()).getAbsolutePath();
JavaCore.setClasspathVariable(JUnitPlugin.JUNIT_HOME, new Path(fullPath), null);I would like to suggest that ME adopt similar code since I have experienced the same problem on 2 different systems and in the past.
Riyad KallaMemberbinyan,
You are the greatest! You really ran this down entirely yourself and got a fix committed to the Eclipse code base; great work!I have passed the message onto the devs so we can reflect necessary changes on our end. Again, thank you for the help.
-
AuthorPosts