Summary: | Batch compiler should check if java home is null when trying to set the extDirs and endorsed dirs | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Olivier Thomann <Olivier_Thomann> | ||||
Component: | Core | Assignee: | Olivier Thomann <Olivier_Thomann> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | CC: | daniel_megert, philippe_mulet | ||||
Version: | 3.2 | ||||||
Target Milestone: | 3.2 RC3 | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Olivier Thomann
2006-05-01 14:29:12 EDT
Created attachment 39972 [details]
Proposed fix
The patch is trivial. It simply adds null checks when using javaHome for settings extdirs and endorsed dirs.
Candidate for RC3?
+1 for 3.2RC3 Dani - would you pls cast your vote ? Trivial fix for batch compiler. Approving for 3.2 RC3. Fixed and released in HEAD. *** Please note: you first have to post the intended bug(s) to the releng list so that others can veto it, see: http://www.eclipse.org/eclipse/development/freeze_plan_3.2.html My understanding was to send the list of bugs fixed. But I didn't understand that the bug list had to be submitted prior to releasing them. It is a notification, not a vote. Did I miss anything? It says: "Announce bug numbers of ***intended*** ... My understanding in the >RC2 phase is that any component lead can veto any change at this time. Though that rarely happens. Verified using N20060503-0010 for 3.2RC3 by creating the executable of the batch compiler using gcj. When running this executable, the java.home property is not set. |