| jar undesirably included in classpath [message #161394] |
Tue, 21 February 2006 12:12 |
Eclipse User |
|
|
|
A jar in my project is getting automatically included in the classpath
when I run the project, and there seems to be no way to stop this.
Here's the scenario:
The project is developed in Eclipse, but is also supposed to allow
someone to check it out and build it without Eclipse. So it has an Ant
script that builds the project's jar. I occasionally run this script
and leave the jar hanging around, since some other projects depend on it.
But while I am using Eclipse, I do not constantly re-run the Ant script
to update the jar. So the jar is usually out of date.
Unfortunately, when I run the project, sometimes when I get errors and
try to click on the reported line number, Eclipse complains that the
line number is not valid, or that there is no source attachment for the
jar. In other words, it reveals that it is actually using the jar,
instead of the classfiles compiled from the actual source.
This is the case even when the "User Entries" item in the "Classpath"
tab of the project "Properties" dialog does *not* include the generated
jar. In fact, I can find *no* explicit indication that this jar is
supposed to be in the classpath. Nonetheless, it obviously is.
I have a suspicion that WTP may be doing this, rather than just the
basic Eclipse, because I know that WTP has some "automagic" things that
set up the classpath.
How can I stop this jar file from being included, short of deleting it?
I am using WTP 1.5M4, with all the recommended "drivers", freshly installed.
|
|
|
Powered by
FUDForum. Page generated in 0.02854 seconds
Home