This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Adding Compiler Collections causes all projects and all build targets to use the new Compiler Collection. | ||
---|---|---|---|
Product: | cnd | Reporter: | dustin_mccartney <dustin_mccartney> |
Component: | -- Other -- | Assignee: | Thomas Preisler <thp> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | ||
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
dustin_mccartney
2007-11-11 11:37:21 UTC
yes, it shouldn't. Please, review http://www.netbeans.org/issues/show_bug.cgi?id=120845 seems to be duplicate Yes, this bug appears to be the general case that is described in bug 120845 (http://www.netbeans.org/issues/show_bug.cgi?id=120845). However, I humbly disagree with sergius' assertion in bug 120845 that the use-case and impact are very small. 1) If adding/removing Compiler Collections causes all projects and build targets to have their user choosen Compiler Collection to change without warning, it can cause: a) Confusion on the part of the user when they go to build a project/target and all of a sudden their compilation changes (target version number, platform target; ie: Linux_x86 project is now building MacOSX_PPC) and/or fails because the project is using a different Compiler Collection. b) Frustration on the part of the user because now EVERY project and EVERY build target now needs to be fixed. In my case, I have 6 projects, each with 8 build targets. That is currently 48 changes I need to make every time I add/or remove a "Compiler Collection", which is unacceptable. I will be adding more projects, so this problem will only get worse. c) Reasons 'a' and 'b' render the usage of "Compiler Collections" unworkable in a professional environment and force the user to look elsewhere to get the job done. 2) I suspect that this bug is related to bug 121675 (http://www.netbeans.org/issues/show_bug.cgi?id=121675). I am not familiar with the code, but I wouldn't be surprised if (in bug 121675) the Compiler Collection is indeed saved with the project settings but is then getting reset when Netbeans loads up and registers it's "Compiler Collections" (vis a vis, this bug or similar). *** This issue has been marked as a duplicate of 120845 *** |