Bug 278246 - extraClasspathEntries should support specifying plug-in bundle jars
Summary: extraClasspathEntries should support specifying plug-in bundle jars
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 3.5   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Ant-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-28 12:11 EDT by David Green CLA
Modified: 2019-09-06 16:09 EDT (History)
6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Green CLA 2009-05-28 12:11:23 EDT 
It should be possible to contribute plug-in jars to the Ant classpath, possibly via extraClasspathEntries.

There's no technical reason that I'm aware of why plug-in jars could not be used to contribute to the Ant classpath.  In fact, Mylyn WikiText provides plug-in jars as part of the stand-alone distribution which can simply be used on the Ant classpath, unmodified.

Related to (blocks) bug 273325
Comment 1 David Green CLA 2009-07-13 18:02:00 EDT 
It would be great to get some feedback on this feature request.  (Is anyone watching platform-ant-inbox@eclipse.org?)
Comment 2 Darin Swanson CLA 2009-07-13 20:26:30 EDT 
There are several people watching but very little to no enhancement work planned for Platform Ant.
Comment 3 Chris Aniszczyk CLA 2009-07-13 20:27:45 EDT 
Darin, off the top of your head, does ant support the platform urls?

ie., platform:/plugin/blah/...
Comment 4 Darin Swanson CLA 2009-07-13 20:29:41 EDT 
Memory is hazy but I think it does...
Comment 5 Nick Edgar CLA 2009-10-22 10:18:22 EDT 
+1
Comment 6 Eclipse Webmaster CLA 2019-09-06 16:09:17 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.