Bug 40664 - certain classpath variables are not persisted at eclipse shutdown
Summary: certain classpath variables are not persisted at eclipse shutdown
Status: CLOSED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: 3.0 M7   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2003-07-23 12:18 EDT by Morgan Delagrange CLA
Modified: 2009-08-30 02:09 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Morgan Delagrange CLA 2003-07-23 12:18:34 EDT
How to reproduce: create a classpath variable called "BCOMROOT", and set it to
some path.  Shutdown and restart Eclipse.  The variable BCOMROOT will be gone. 
This is the only variable I've found so far that exhibits this behaviour. 
Several developers in my organization have reported the same problems with that
variable.
Comment 1 Morgan Delagrange CLA 2003-07-23 12:39:24 EDT
exists on at least Eclipse 2.1, 2.1.1 and 3.0M2.  Did not exist in Eclipse 2.0.
Comment 2 Philipe Mulet CLA 2003-07-24 08:01:56 EDT
Pls investigate
Comment 3 Nick Teryaev CLA 2003-07-29 11:50:23 EDT
not reproduced in Eclipse M2 with recent eclipse.jdt.core (07/29).
i went to preferences | java | classpath variables. create a new var (tried 
both file and folder), exited eclispe, started it again, variable was there. i 
think that it depends on the folder BCOMROOT it points to.
Comment 4 Morgan Delagrange CLA 2003-07-29 15:20:45 EDT
Odd.  I tried installing the JDT core plugin from last night's build, and I
still cannot create a BCOMROOT variable.  I tried using the variable name "BLAH"
against the same folder, and it persists just fine.  I tried using the BCOMROOT
variable name, but pointed it to a folder for which I have an existing variable;
that still fails to persists on shutdown.

One possible factor is that when I initially created the variable, I used a
custom plugin with the following API call:

<pre>
        IPath bcomRoot = JavaCore.getClasspathVariable("BCOMROOT");

        Shell shell = getShell();

        if (bcomRoot == null) {
            DirectoryDialog dialog = new DirectoryDialog(shell);
            dialog.setMessage("Select the location of your BCOMROOT.");
            String path = dialog.open();

            if (path == null) {
                return;
            }

            bcomRoot = new Path(path);

            JavaCore.setClasspathVariable(
                "BCOMROOT",
                bcomRoot,
                new NullProgressMonitor());

        }
</pre>

Now every time I try to create the BCOMROOT variable, either through the
standard GUI or through the API, it does not persist on shutdown.  It's possible
that using the API has fouled up the variable persistance in some way.  I
suppose that if there is a convenient way to delete my Eclipse configuration, I
can try creating a BCOMROOT variable without using the API.
Comment 5 Jerome Lanneluc CLA 2003-08-20 07:55:50 EDT
Sorry but I cannot reproduce your problem. Is the name of the folder the 
variable points to special in some way?
Comment 6 Jerome Lanneluc CLA 2003-08-22 11:10:17 EDT
Please reopen when you have more information.
Comment 7 Philipe Mulet CLA 2004-01-27 08:16:02 EST
Closing as no response in a long time.
Comment 8 Denis Roy CLA 2009-08-30 02:09:42 EDT
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.