Bug 186113 - [model] classpath variable deprecation messages not initialized when called
Summary: [model] classpath variable deprecation messages not initialized when called
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.4 M2   Edit
Assignee: Frederic Fusier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-09 06:19 EDT by Benno Baumgartner CLA
Modified: 2007-09-18 03:20 EDT (History)
2 users (show)

See Also:

Attachments
Proposed patch (4.79 KB, patch)
2007-08-17 10:52 EDT, Frederic Fusier CLA 		no flags Details | Diff
New proposed patch (7.38 KB, patch)
2007-08-18 13:54 EDT, Frederic Fusier CLA 		no flags Details | Diff
Show Obsolete (1) 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 Benno Baumgartner CLA 2007-05-09 06:19:54 EDT 
I20070503-1400

1. Start workspace
2. call JavaCore.getClasspathVariableDeprecationMessage("JRE_LIB")
Is:
 null
Should:
 return deprecation message for JRE_LIB

Problem seams to be that deprecatedVariables is only initialized in JavaCore#getClasspathVariableInitializer(...).
Comment 1 Frederic Fusier CLA 2007-08-17 10:52:07 EDT 
Created attachment 76309 [details]
Proposed patch
Comment 2 Frederic Fusier CLA 2007-08-18 13:54:34 EDT 
Created attachment 76373 [details]
New proposed patch

Better patch as it does not need to initialize classpath variable to return the deprecation message.

Note that this patch also includes the fix for bug 200449.
Comment 3 Frederic Fusier CLA 2007-08-18 14:01:19 EDT 
Released for 3.4M2 in HEAD stream.
Comment 4 Eric Jodet CLA 2007-09-18 01:11:36 EDT 
(In reply to comment #3)
Verified for 3.4 M2 using build I20070917-0010.