Bug 26061 - Changes to Ant classpath don't persist
Summary: Changes to Ant classpath don't persist
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: 2.1 M3   Edit
Assignee: Darin Wright CLA
QA Contact:
URL:
Whiteboard:
Keywords: core, ui
: 25863 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-11-12 17:01 EST by Joe Szurszewski CLA
Modified: 2002-11-18 13:51 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joe Szurszewski CLA 2002-11-12 17:01:16 EST
Go to Preferences-->External Tools-->Ant-->Classpath.  Remove the 1.5.1 versions of 'ant.jar' & 'optional.jar' entries.  Now add corresponding entries from a previous version of Ant (like 1.4.1).  Save & exit workbench.  Restart workbench and notice in Prefs that the 1.5.1 jars are back.
Comment 1 Darin Swanson CLA 2002-11-12 19:54:38 EST
You guys got to get a browser that wraps the lines...
Comment 2 Darin Swanson CLA 2002-11-12 22:32:44 EST
*** Bug 25863 has been marked as a duplicate of this bug. ***
Comment 3 Darin Swanson CLA 2002-11-12 22:35:11 EST
Fixed in AntCorePreferences
Comment 4 Darin Swanson CLA 2002-11-12 22:40:05 EST
Please verify (Darin W).
It would be great if this could get into M3...I am not sure of what state the 
builds are in...
Comment 5 Darin Wright CLA 2002-11-13 10:56:08 EST
Verified it works with a new workspace. With an old workspace, this does not 
seem to work, even when I "Restore Defaults". I would expect that when I 
restore defaults that this would reset the list of 'runtime' jars such that it 
becomes portable? 
Comment 6 Darin Wright CLA 2002-11-13 10:56:36 EST
Adding DS as CC to see last comment.
Comment 7 Darin Swanson CLA 2002-11-14 12:10:07 EST
I will look into this more this evening.
Comment 8 Darin Swanson CLA 2002-11-18 13:00:06 EST
I cannot reproduce your problem:
I created a workspace using an M2 install
I modified the ant runtime classpath
Exited
Opened the workspace using an M3 install

The ant runtime classpath was correct and the changes I had made were in the 
additional classpath entires (not perfect but constants changed between the 
builds and the user will still get the correct behavior).  Hitting Restore 
defaults just worked.
Comment 9 Darin Wright CLA 2002-11-18 13:51:30 EST
Verified.