Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[pde-dev] Incorrect warning about referenced class in antTasks extension

A while back I asked questions on the platform newsgroup about some extra warnings that started when I installed Eclipse 3.2M4 (see topic "org.eclipse.ant.core.antTasks warnings in 3.2M4" dated Dec 18). Later I entered a bugzilla on it: https://bugs.eclipse.org/bugs/show_bug.cgi?id=121691

Wassim Melhem closed this bug as "RESOLVED INVALID" explaining that the jar in question can be added to the .classpath of the plugin. I don't want to do that and I base this on the following section in the Eclipse "Platform Plug-in Developer Guide":

http://help.eclipse.org/help31/topic/org.eclipse.platform.doc.isv/guide/ant_developing.htm

The fact that adding the jar file to the .classpath will work at runtime is of minor interest. It does not work in a self-hosting scenario and that's what I'm in most of the time when I'm developing and that's the only time I have an interest in the warnings.

I have several reasons not to modify my .classpath each time I want to debug or test. One is of course that I don't want to mess up version history when there's no need for it. I really prefer to have my ant-tasks in a separate jar file that I maintain separately. Judging from the way that several of the eclipse platform plugins are constituted, I'm not alone.

And even if I can make it work using a redundant .classpath entry, why must I add the jar-file in two places? The plugin.xml entry ought to be enough to silence the warnings.

I still consider this a bug. What do you think?

Regards,
Thomas Hallgren



Back to the top