Bug 24699 - Ant classpath should be separated into two components?
Summary: Ant classpath should be separated into two components?
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P2 enhancement (vote)
Target Milestone: 2.1 M4   Edit
Assignee: Darin Wright CLA
QA Contact:
URL:
Whiteboard:
Keywords: core, ui
Depends on:
Blocks:
 
Reported: 2002-10-11 10:55 EDT by Darin Wright CLA
Modified: 2002-11-25 11:59 EST (History)
0 users

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 Darin Wright CLA 2002-10-11 10:55:02 EDT 
Related to bug 19899, I think that the Ant classpath should really be separated 
into two components: (1) Eclipse Ant Support, and (2) Additional entries. 

The problem is that if a user adds an aditional entry, the classpath is then 
saved. If a new eclipse install is then used - the ant support portion may now 
be invalid. There should be a way to say "use default Eclipse ant support", and 
use these additional entries, without being hard-coded to a location on disk 
for the "Eclipse ant support".

This is related to the ability to use a "pluggable" Ant implementation.
Comment 1 Darin Swanson CLA 2002-11-04 18:10:06 EST 
Implemented.
Please verify.
Comment 2 Darin Wright CLA 2002-11-11 16:26:11 EST 
The classpath is split into two areas, but it appears it is still saved as 
explicit paths when I add to the classpath.

(1) Create a new workspace.
(2) add an entry to the "additional classpath entries" area.
(3) Save the workspace
(4) launch a new install of eclipse from a different directory, on the same 
workspace

-> the "Runtime" porition of the path still points to my previous eclipse 
install, but should point to my new Eclipse install.

(Perhaps we should fix this when we add classpath support to Ant launch 
configs).
Comment 3 Darin Swanson CLA 2002-11-18 11:18:36 EST 
I believe the behavior you were seeing was a side effect of bug 26061.
I just retested and the runtime classpath updated as expected for the different 
install locatins.
Comment 4 Darin Swanson CLA 2002-11-18 11:19:02 EST 
Please verify.
Comment 5 Darin Wright CLA 2002-11-25 11:59:15 EST 
Verified.