Bug 6488 - Classpath Variables (allow plugins to reserve some)
Summary: Classpath Variables (allow plugins to reserve some)
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 2.1 RC1   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-11-30 16:30 EST by Richard Kulp CLA
Modified: 2003-02-14 09:19 EST (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 Richard Kulp CLA 2001-11-30 16:30:06 EST 
Plugins should be able to mark classpath variables that they create as reserved 
so that the user can't accidently change (just like JRELIB, ... are reserved). 
They should have the option of marking them reserved.
Thanks,
Rich Kulp
Comment 1 Philipe Mulet CLA 2001-11-30 18:45:36 EST 
Interesting idea. For info, JDT/Core owns no variable in particular. JDT/UI 
defines the trio JRE_* and show them as reserved.

I believe though that there should be a mechanism for plugins to declare 
classpath variables which then are recognized as such, and the respective 
plugin inference would be the only way to update them.

JDT/Core only defines an infrastructure for defining and using them, it does 
not come with any preferred ones.
Comment 2 Philipe Mulet CLA 2002-03-14 12:47:22 EST 
Will consider post 2.0
Comment 3 Philipe Mulet CLA 2003-02-14 09:18:26 EST 
Closing, registered variables are detectable by asking:

JavaCore.getClasspathVariableInitializer(varName) != null
Comment 4 Philipe Mulet CLA 2003-02-14 09:19:00 EST 
Closing