Community
Participate
Working Groups
This request is related to bug 13921. We have multiple different 'projects' in our CVS repository, each of which uses different settings (Values for ${PROPERTIES}, CLASSPATH settings, etc.) for running ANT. Bug 13921 requests that it be possible to designate a set of ${PROPERTIES} for running ANT on a per-project basis. This would relieve the end user of the necessity of having to key the ${PROPERTIES} definitions into the ANT Wizards for every single build.xml in a project. In a similar way, Eclipse 2.0 currently has ANT configuration settings for CLASSPATH, Tasks and Types set globally. However, this is a pain, because these settings are more properly broken down to project-level granularity. The CLASSPATH I need to build project A might be different from the CLASSPATH I need to build project B. In sum, I would request that the configuration settings for ANT be (1) Made richer (defining per-project ${PROPERTIES}, etc.) and (2) Moved to the individual project Properties context menu, rather than appearing in the global 'Window->Preferences' menu.
Not planned for 2.0. Defer.
Reopening for consideration. Related to bug 13921.
*** Bug 25453 has been marked as a duplicate of this bug. ***
The plan for 2.1 is to use launch configurations to configure ant scripts. This way you get configurability per configuration (and if you want, more than one configuration per script - i.e. N configs per script is possible). However, we need to the classpath properties to the configs.
Classpath and properties can be defined per launch configuration or the launch configuration can use the global preferences.
Please verify (DarinW).
Verified.
