Bug 19899 - If the user never changes the Ant classpath, it should always be computed
Summary: If the user never changes the Ant classpath, it should always be computed
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P2 normal (vote)
Target Milestone: 2.1 M2   Edit
Assignee: Darin Wright CLA
QA Contact:
URL:
Whiteboard:
Keywords: core
Depends on:
Blocks:
 
Reported: 2002-06-11 09:59 EDT by Rodrigo Peretti CLA
Modified: 2002-10-11 10:50 EDT (History)
2 users (show)

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 Rodrigo Peretti CLA 2002-06-11 09:59:19 EDT 
build F2

Currently, the first time Eclipse runs, the Ant classpath is computed and 
saved on exit even if the user has not changed it. If the user gets a new 
version of Eclipse and installs it in a different location, the Ant classpath 
is incorrect.
In order to make it better the classpath should only be saved if the user has 
changed it. Otherwise, it should always be computed.
Comment 1 Rodrigo Peretti CLA 2002-06-11 09:59:33 EDT 
Defer after 2.0.
Comment 2 Rodrigo Peretti CLA 2002-07-29 15:50:48 EDT 
Reconsider.
Comment 3 Darin Swanson CLA 2002-09-25 14:05:48 EDT 
If ant classpath is the default ant classpath, it is not stored as a preference.
This has the side effect of the default ant classpath always being computed if 
no custom classpath is set.
Comment 4 Darin Swanson CLA 2002-09-25 14:06:42 EDT 
Please verify changes to AntCorePreferences.
Comment 5 Darin Swanson CLA 2002-09-27 11:31:01 EDT 
Please verify (Darin W)
Comment 6 Darin Swanson CLA 2002-09-30 10:26:51 EDT 
Note that if the user has been using a workspace for some time and has changed 
the installed version of Eclipse, the default classpath will not be correct.  
The user will have to "restore default" on the External Tools->Ant preference 
page to fix the problem.  After this single intervention by the user, older 
workspaces will stay up to date.
Comment 7 Rodrigo Peretti CLA 2002-09-30 10:52:16 EDT 
That is exactly why I've opened this bug :-)
Comment 8 Darin Swanson CLA 2002-10-04 12:00:15 EDT 
If a workspace has been used on the old codebase there is no way to tell that 
the persisted classpath is an old default classpath.  Any workspace that is 
only used on the new codebase can never get into this state (the default 
classpath is never persisted).
Comment 9 Darin Swanson CLA 2002-10-11 10:00:52 EDT 
Reopening to reassign for M2 verification.
Comment 10 Darin Swanson CLA 2002-10-11 10:01:23 EDT 
Please verify Darin W
Comment 11 Darin Wright CLA 2002-10-11 10:50:11 EDT 
Verified. (But I'm going to open a new feature request... :-)