Bug 60342 - Changes to CLASSPATH VARIABLES are lost when I close my workspace.
Summary: Changes to CLASSPATH VARIABLES are lost when I close my workspace.
Status: CLOSED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1.2   Edit
Hardware: PC Windows 2000
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2004-04-28 18:06 EDT by Yakov Sobolev CLA
Modified: 2009-08-30 02:05 EDT (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 Yakov Sobolev CLA 2004-04-28 18:06:54 EDT 
Changes to CLASSPATH VARIABLES are lost when I close my workspace.
I make a change to classpath variable, apply/save changes. Close workspace. 
When I reopen it - all changes that I made are lost. 
Where do you save CLASSPATH VARIABLES?
May be I can manually edit that file?
Comment 1 DJ Houghton CLA 2004-04-28 20:14:55 EDT 
Which Eclipse build are you using? 

I am unable to reproduce this with either 2.0.2 or the integration build from 0427.
Comment 2 Yakov Sobolev CLA 2004-04-29 10:28:51 EDT 
Eclipse Platform:
Version: 2.1.2
Build id: 200311030802
Comment 3 John Arthorne CLA 2004-04-29 16:35:34 EDT 
Do you have a large number of classpath variables? (see bug 39289).

Anything reported in the log file? (workspace/.metadata/.log)
Comment 4 Yakov Sobolev CLA 2004-04-29 16:46:08 EDT 
We have 33 classpath variable
We are having problem with WAS_50_PLUGINDIR variable after converting from WSAD 
5.0 to WSAD 5.1
It always points to: C:/Program Files/IBM/WebSphere Studio/Application 
Developer/v5.1.1/runtimes/base_v5_stub folder
We change it to point to: C:/Program Files/IBM/WebSphere Studio/Application 
Developer/v5.1.1/runtimes/base_v51
But after we close and reopen WSAD - it pomts to /base_v5_stub folder again.
The bug that you mentioned saying: "...Since release 2.0, variables are no 
longer stored in persistent properties... "
Comment 5 John Arthorne CLA 2004-05-12 11:59:29 EDT 
Classpath variables are managed by JDT core
Comment 6 Philipe Mulet CLA 2004-05-13 07:03:15 EDT 
Can you reproduce this behavior on a recent 3.0 build ?
If so, then please provide exact steps to reproduce.
Classpath variables are normally persisted across sessions, and reinitialized 
only if a registered initializer is detected.

Once information is available, please reopen.

Classpath variables are stored in plugin preference store, this could be an 
area also to look for a bug. If unable to read it back, they could appear as 
unbound. So, is there anything available in .log file ?
Comment 7 Yakov Sobolev CLA 2004-05-13 09:54:03 EDT 
I resolved that issue by copying missing jar's in the old directory. workaround
Comment 8 Frederic Fusier CLA 2005-02-17 09:47:09 EST 
Closing as never got requested information
Comment 9 Denis Roy CLA 2009-08-30 02:05:11 EDT 
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.