Bugzilla – Full Text Bug Listing
| Summary: | [ExternalTools] Bad jar locations displayed on preference page | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Adam Schlegel <Adam_Schlegel> |
| Component: | Ant | Assignee: | Platform-Ant-Inbox <platform-ant-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | simon_arsenault |
| Version: | 2.0 | Keywords: | core, ui |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
Should use IPluginDescriptor.find. Setting resolution to later. The extraClasspathEntries extension point is the supported means for adding JARs to the Ant runtime classpath. No work planned. As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you. |
A Jar file can be contributed to Eclipse's Ant via a fragment. Unitl the External Tools support was added, this was the only way to add jar files to Ant's classpath for both UI and headless execution. It remains the only way to add jars for in the headless case, since the External Tools support is all in the UI. Jars added in this manner have are listed with an incorrect path in the External Tools->Ant preference page. The displayed path shows a jar in the plugins\org.apache.ant directory, when they really exist in the fragment's directory. Such jars are on the classpath correctly, so Ant scripts that depend on them work correctly. An example fragment.xml that contributes a jar to org.apache.ant in this manner is given below. <?xml version="1.0" encoding="UTF-8"?> <fragment id="org.eclipse.foo" name="Foo Fragment" version="1.0.0" plugin-id="org.apache.ant" plugin-version="1.4.1"> <runtime> <library name="foo.jar"> <export name="*"/> </library> </runtime> </fragment>