Community
Participate
Working Groups
When specifying JARs or folders for the Ant classpath it should be possible to specify / use variables.
Consider for 2.1
Deferred for post 2.1 consideration
More complete description from bug 29861: However the Ant classpath configuration does not allow jar references relative to project locations, so the .launch files contain absolute paths, eg c:\dev\myproject\junit.jar, which is doesn't make the common launch configurations very useful when the developers are not all running on the same platform or are using different directory structures. The global ant preferences should also be project or workspace relative as well to aid portability.
*** Bug 29861 has been marked as a duplicate of this bug. ***
I add my vote for this one. Ant and Eclipse are create tools and this would leverage their integration one step above from what we can see in other environments.
*** Bug 37848 has been marked as a duplicate of this bug. ***
Reopen for consideration in 3.0
I have released changes to allow specifying Ant classpath entries and property files relative to the workspace location. Currently only supported on the custom launch configuration classpath and not on the global Ant runtime classpath. The global Ant runtime classpath does not support workspace relative entries as these are stored in the Ant Core preferences and the support for launch variables lives in debug core which Ant core has no knowledge about.
Variable support will soon be available in org.eclipse.core.variables. Moving to M5.
I have deprecated the methods that are going to have to change / be replaced in AntCorePreferences.
The jars added to the Ant core runtime classpath can be workspace relative. The Ant core will handle variables but we need to fully expose this in the UI.
UI work to allow use of any variable will have be attempted in M6
With M6 focus set on reducing the backlog of bugs, this enhancement will have to wait until M7
Both Java and Ant are planning on adding something to the UI to make this easier in M9
Is this still an issue? After the work done earlier this year on the classpath tab, it seems that entries are now being resolved relative to the workspace.
But there is no means to add entries that are anything else BUT relative to the workspace. We have so many variables... :-)
The classpath tab is nice in 3.0 M8 but I'm still missing a button that is available in the Java build path "Add Variable...". This will bring up a dialog for selecting a variable and extending it. This feature is necessary to share launch configs with JARs in the classpath which are OUTSIDE the workspace. It's impossible that every developer with have the JAR at "D:\myAppServer\libs\tata.jar". It's easier to specify "APP_SERVER_HOME/libs/tata.jar". The platforms variables should be reused for this.
This should just come out of bug 40766. Assigning to Kevin to make sure :-)
Bug 40766 makes this fix possible, but we still need to make some UI changes in ant land to expose the variables to users. Attached patch for changes to: AntClasspathTab AntLaunchConfigurationMessages.properties AddVariableStringAction (new) DialogSettingsHelper (new) DarinS, see Bug 40766 comment 8 for list of files you will need to update before the patch will work.
Created attachment 9299 [details] patch to org.eclipse.ant.ui
I logged two bugs: bug 57838 bug 57839 Patch applied. Thanks kevin.
Please verify DarinW.
Verified.
