Bugzilla – Full Text Bug Listing
| Summary: | Non-Java projects get re-built when changing a compiler setting on the preference page | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Michael Rennie <Michael_Rennie> | ||||
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P4 | CC: | daniel_megert, deepakazad, farmboy0, markus.kell.r, Markus.Milleder, Olivier_Thomann | ||||
| Version: | 3.7 | Keywords: | performance | ||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | stalebug | ||||||
| Attachments: |
|
||||||
Only building the Java projects would be wrong as non-Java projects could depend on the build state including problem markers. Like for Java projects project relations might not be defined via 'Project References'. Suggest to close as WONTFIX or even INVALID. In org.eclipse.jdt.internal.ui.util.CoreUtility.BuildJob.run(IProgressMonitor), we currently request a full build of the workspace. We could change this to behave more similar to the changes in project-specific settings, i.e. fully build all Java projects and then request an incremental build of the workspace. *** Bug 230859 has been marked as a duplicate of this bug. *** This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |
Created attachment 174330 [details] project that demos the problem build: I20100713-0800 If you have projects in your workspace that do not have a Java nature, they will be re-built anyways if you change a workspace compiler option (on the Java > Compiler > Errors/Warnings preference page). The attached project demonstrates the problem. Steps 1. import the attached project into your workspace 2. change a Java compiler setting and click yes to perform a full build. Expected All my Java project would be re-built Happens all of my Java projects get built (OK) and all of the non-Java projects get built. to ensure the test project is built, it includes an external tool builder that prints the following to the console: Buildfile: <workspace_path>/JS/build.xml default: [echo] I was built BUILD SUCCESSFUL Total time: 878 milliseconds