Bug 39289 - Java Classpath variables lost after restart
Summary: Java Classpath variables lost after restart
Status: RESOLVED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 1.0   Edit
Hardware: PC Windows 2000
: P3 major (vote)
Target Milestone: 3.0 M3   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-24 16:29 EDT by Sandeep Grewal CLA
Modified: 2003-10-06 04:39 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sandeep Grewal CLA 2003-06-24 16:29:40 EDT
We have set 67 classpath variables which our components refer. But when we open 
WSAD now, all these disappear and we have to manually add these again. 
                                                                 
The variables are added using Window --> Preferences --> Java --> Classpath 
Variables

1. Is there any file in Eclipse 1.0 where the variables can be 
added?             
                                                                 
2. Is there a limit for the number of variables? When this is exceeded, they 
all disappear and only the default variables show up after startupup after 
startup   

Steps to reproduce: 
1. Please add 65-70 variables using Window --> Preferences --> Java --> 
Classpath Variables
2. Shutdown Eclipse and restart it, the variables should have disappeared 
leaving only the default ones.
Comment 1 Mischa Christen CLA 2003-07-18 02:57:49 EDT
Have same problem after creating more that one workspace.
Comment 2 John Arthorne CLA 2003-07-24 12:55:26 EDT
Confirmed the bug.  If you create a folder whose path is 256 characters, and
create very long variable names, you can get it to fail with about 20 variables.

This is because classpath variables in 1.0 were stored in an IResource
persistent property, which has a limit of 2KB per property.  It is likely that
the CoreException was not correctly handled on IResource.setPersistentProperty.

So, to answer your questions:

1. No, there is no file that you can modify to add variables.  These were stored
in a binary b-tree file that cannot be directly modified.

2. Yes, there was a limit on the number of variables in 1.0.

Since release 2.0, variables are no longer stored in persistent properties. 
Since no further maintenance releases are planned on 1.0, it is not likely that
this will be fixed.