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.

Bug 163525 - Need API to replace existing project property nodes
Summary: Need API to replace existing project property nodes
Status: NEW
Alias: None
Product: cnd
Classification: Unclassified
Component: Project (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@cnd
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-23 19:51 UTC by _ gordonp
Modified: 2014-04-14 14:30 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
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 _ gordonp 2009-04-23 19:51:30 UTC 
This primarily refers to the Build subnodes (C Compiler, C++ Compiler, etc). What
happens to the C++ Compiler node if the chosen toolchain doesn't have a C++
compiler? Nothing, its still shown. So that is the 1st part of this issue.

Also, MC's current IDE has a very nice tabbed window for setting compiler options
(more along the lines of what CND has discussed for several years, but never
implemented). They would like to either replace the subnode completely, or (at a
minimum) be able to override the property editor to Additional Options.
Comment 1 vincesheard 2010-06-02 16:34:10 UTC 
MC has implemented their own type of project so this is not as high a priority for them.
I could see it as an advantage to other uses wanting to use cnd projects and be able to remove nodes in the tree. But unless others want this I would not request it to be a high priority for MC anymore.
Comment 2 Thomas Preisler 2010-06-02 16:47:43 UTC 
Great. I will drop priority to p3.

We want to implement properties in xml layer and this will allow much greater control over the properties.