Summary: | Make all ANT configuration defined at config level | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | David Bailey <david.bailey> |
Component: | Ant | Assignee: | Darin Wright <darin.eclipse> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | mhilpert, rodrigo |
Version: | 2.0 | Keywords: | core |
Target Milestone: | 2.1 M4 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
David Bailey
2002-05-07 09:03:45 EDT
Not planned for 2.0. Defer. *** 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. |