Bug 211669 - Allow adding User Libraries and Classpath Variables in an Ant Runtime Configuration's classpath
Summary: Allow adding User Libraries and Classpath Variables in an Ant Runtime Configu...
Status: REOPENED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 3.4   Edit
Hardware: All All
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform-Ant-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-01 06:09 EST by Isaac Shabtay CLA
Modified: 2014-02-25 07:08 EST (History)
4 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 Isaac Shabtay CLA 2007-12-01 06:09:46 EST 
When creating a Run Configuration for an Ant build file, the developer has the possibility of adding items to the classpath via the "Classpath" tab.

In contrary to other Run Configurations, the Ant Run Configuration dialog does not permit the user to add a "User Library" to the classpath (currently accepts individual JARs, external JARs, folders and variables).

It may be useful for developers to be able to specify custom pre-defined User Libraries as classpath entries in Ant Run Configurations.
Comment 1 Isaac Shabtay CLA 2007-12-01 06:11:37 EST 
On the same note, and for the same reasons, perhaps enabling the developer to also add Classpath Variables?
Comment 2 Martin Oberhuber CLA 2009-05-13 04:36:38 EDT 
In what respect is a "User Library" different than a folder or classpath variable? Is there anything you *can not* do with Eclipse today, or is there a workaround?

I can't really see the problem here. Perhaps we could resolve this WORKSFORME as per Eclipse 3.5 ?
Comment 3 Michael Rennie CLA 2009-05-13 09:36:10 EDT 
agreed
Comment 4 Darin Wright CLA 2009-05-13 09:53:28 EDT 
(In reply to comment #2)
> In what respect is a "User Library" different than a folder or classpath
> variable? Is there anything you *can not* do with Eclipse today, or is there a
> workaround?
> I can't really see the problem here. Perhaps we could resolve this WORKSFORME
> as per Eclipse 3.5 ?

I think it's just convenience... If there is a user library already set up that contains other libraries, perhaps it's just a more convenient way to add things to the classpath.
Comment 5 Isaac Shabtay CLA 2009-05-15 18:31:49 EDT 
Hi Martin,
Sorry, was away for a few days.

Darin's response was correct. Under certain circumstances, using a classpath variable or a user library is a much more convenient way to add things to the classpath than attaching individual JAR files. This also holds in case I'd like to store the Launch Configuration in my SCM and don't want to hold absolute, machine-specific locations there.

There's nothing broken in the current behavior - it is just inconsistent (other places within Eclipse allow you to add user libraries and classpath variables. For example, you can add a user library to a Java Launch Configuration... so why not allow it for Ant Launch Configurations?)


Re-opening...