Bug 171049 - [build path] use the new 'deprecated' and 'read-only' classpath variables
Summary: [build path] use the new 'deprecated' and 'read-only' classpath variables
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P2 enhancement (vote)
Target Milestone: 3.3 M5   Edit
Assignee: Markus Keller CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 172207
Blocks:
  Show dependency tree
 
Reported: 2007-01-19 09:39 EST by Martin Aeschlimann CLA
Modified: 2007-02-06 11:55 EST (History)
1 user (show)

See Also:

Attachments
Fix (47.24 KB, patch)
2007-02-01 10:39 EST, Markus Keller CLA 		no flags Details | Diff
View All 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 Martin Aeschlimann CLA 2007-01-19 09:39:21 EST 
I20070119

JDT core will soon release support to mark classpath variables as deprecated and read-only (bug 138599).

We can now
- mark the JUnit varibales as deprecated:
  Message: Use the JUnit container instead
- support 'read-only' in the VariableBlock:
  Disable 'Edit' for read-only vars and a '(non modifiable)' to their label.

I suggest to change this also for JRE_LIB: Ask jdt.launching to use the new flags, remove all special code dealing with the JRE variables.
Comment 1 Markus Keller CLA 2007-02-01 10:39:59 EST 
Created attachment 58016 [details]
Fix
Comment 2 Markus Keller CLA 2007-02-01 10:41:05 EST 
Released fix to HEAD.
Comment 3 Benno Baumgartner CLA 2007-02-06 11:55:56 EST 
verified in I20070206-0010