Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 354092 - [preferences] Java Compiler property page doesn't gray out all widgets (without project specific settings)
Summary: [preferences] Java Compiler property page doesn't gray out all widgets (witho...
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5.2   Edit
Hardware: All All
: P5 minor (vote)
Target Milestone: 3.8 M3   Edit
Assignee: Dani Megert CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-07 11:55 EDT by Szymon Ptaszkiewicz CLA
Modified: 2011-10-26 04:13 EDT (History)
2 users (show)

See Also:

Attachments
Screenshot 1 (37.64 KB, image/png)
2011-08-07 11:56 EDT, Szymon Ptaszkiewicz CLA 		no flags Details
Screenshot 2 (37.79 KB, image/png)
2011-08-07 11:57 EDT, Szymon Ptaszkiewicz CLA 		no flags Details
Patch v1 (1.59 KB, patch)
2011-10-03 12:04 EDT, Szymon Ptaszkiewicz 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 Szymon Ptaszkiewicz CLA 2011-08-07 11:55:48 EDT 
Build id: I20110803-1800

Steps to reproduce:
1. Create new Java project.
2. Open properties dialog for this project.
3. Open Java Compiler page. Note that by default 'Enable project specific settings' is disabled and all widgets below are grayed (see Screenshot 1).
4. Switch to another property page but do not close the dialog.
5. Switch back to Java Compiler page. Note that some widgets are not grayed any more but no action can be done on those widgets (see Screenshot 2).

Reproducible: Always
Comment 1 Szymon Ptaszkiewicz CLA 2011-08-07 11:56:31 EDT 
Created attachment 201047 [details]
Screenshot 1
Comment 2 Szymon Ptaszkiewicz CLA 2011-08-07 11:57:03 EDT 
Created attachment 201048 [details]
Screenshot 2
Comment 3 Markus Keller CLA 2011-08-08 01:25:21 EDT 
Doesn't happen by default, because we always set project-specific settings if the JRE on the classpath is an Execution Environment.

Happens since at least 3.5.2.

This should occur rarely in practice, since using the default JRE is not recommended and not having project-specific compiler settings is error-prone.
Comment 4 Szymon Ptaszkiewicz CLA 2011-10-03 12:04:15 EDT 
Created attachment 204456 [details]
Patch v1

The fix seems to be pretty simple. Markus, what do you think?
Comment 5 Dani Megert CLA 2011-10-04 07:58:48 EDT 
Thanks for the patch.

Fixed in master.
Commit c7b806af990bb18f473187b553334dfb4a271e31
Comment 6 Dani Megert CLA 2011-10-26 04:13:36 EDT 
Verified in 3.8-I20111025-1800.