Community
Participate
Working Groups
Libraries specified via the extra ant classpath entries extention point are not exposed to the user. This could lead to confusing problems. I believe we should allow the user to see this entries and some mechanism to ensure that user supplied classpath entries can be included before the plugin specified entries.
See bug 24699 as well.
I have made an executive decision (ack :-) ) that it is too late in the game for the rework involved for this enhancement. I did make some changes however that will possibly benefit power users: the extra classpath entries are always added last to the classpath. This would allow custom classpath entries to "hide" the extension point specified entries. As well, it should speed up classloading not to constantly be checking for classes in these jars (these URLs were being placed before the Ant URLs).
If you could verify the changes to AntRuntime, AntCorePreferences, AntClasspathTab and the AntClasspathPage. Then mark this bug for later.
I noticed that #getDefaultURLS was removed from AntCorePreferences - however, this is considered a breaking API change? We should leave the method, but deprecated, and delegate to #getExtraClasspathURLs. As well, we should add the "since tag" to the new method.
AntCorePreferences was only promoted to "api" in 2.1. It was internal in 2.0. See bug 19801. I don't believe the changes are required?
OK - it's fine then.
Verified
Oops, I mean...
Later
These are now shown for the configuration classpath tab. For the preferences will show up when tackle bug 53688
Deferred to be handled with bug 55283.
reopening to mark as dup
*** This bug has been marked as a duplicate of 58351 ***