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.
Using NB4 daily build 20041012 (same in NB4 beta 2). I customized project.xml to my liking for tree display of source folders in project view as follows: <view> <items> <source-folder style="tree"> <label>Java Sources</label> <location>${project.dir}/src/java</location> </source-folder> Note the style="tree"! When I open the project properties dialog and simply close it again by clicking ok, a new source-folder element is _added_ with style="packages" instead of "tree", the original one is kept. So I end up with duplicate display of this folder, once as tree, once as packages.
Known issue. Once you start advanced customization of project.xml by hand you should not use Project Properties customizer because its abilities are very limited in this respect and as you can see it can clobber some of your customizations.
NB should at some stage at least give a hint about this fact then - otherwise users who have just accepted that they have to customize project.xml manually are being put off once more, especially when their customization gets lost this way (which I must expect given your comment)! IMO minimal solution for 4.0 would be a comment in the project.xml template generated by NB: "don't use project properties customizer when editing this file manually" or similar.
I agree that the project.xml should at least warn you about GUI customization. The preferable state would be that each panel of the GUI customizer would, when opened, check the existing state of the project.xml and determine if it is in a form that it could have produced itself. If not, the user must have made text edits, so disable that panel (or just the whole customizer, perhaps).
I can easily write text "Do not use Project Properties customizer when editting this file manually." just at the beginning of <general-data> section. OK? Putting it at the beginning of the file would be more complicated.
Sounds good enough for now.
Nonlocalizable message was added: src/org/netbeans/modules/ant/freeform/FreeformProjectGenerator.java; new revision: 1.31; previous revision: 1.30
Should be localizable (taken from a bundle), IMHO.
OK, changed.
*** Issue 51867 has been marked as a duplicate of this issue. ***
Jesse, I'm moving project infrastructure base freeform issues to you.
*** Issue 53390 has been marked as a duplicate of this issue. ***
I think this can be considered a defect. It is permissible for a GUI properties dialog to be unable to display a complete GUI for every possible project.xml configuration. It is not permissible for it to quietly break things that were set up correctly in project.xml via manual editing, even with the warning in project.xml. It may refuse to display a panel, or grey it all out, or show a warning dialog. It could refuse to open the entire properties dialog, or try to permit edits to unrelated parts of project.xml.
I will try to do something for this for 5.0, but not sure if I will have enough time.
*** Issue 73590 has been marked as a duplicate of this issue. ***
Will try to come up with something for 6.0.
This is particularly problematic for us since we are using a project template that lays down a pre-configured freeform ant project. From the standpoint of the end-user, they have never performed any customization on the project.xml and yet they cannot use the "Project Properties" without causing problems. I'm not sure what your schedule is like for 6.0 or whether this is going to make it. At the very least though, it would help us out immensly if you simply added support for a "disableProjectProperties" flag to project.xml that could turn off the Project Properties completely. In our pre-configured project.xml, we could set the disableProjectProperties flag. That would actually be preferable from our standpoint because things like build classpath are actually controlled by another build.properties file that is referenced from both the project.xml and from our build script, so the user should never be using the Project Properties action to do anything. For example we have: <properties> <property-file>build-config.properties</property-file> </properties> ... <java-data xmlns="http://www.netbeans.org/ns/freeform-project-java/1"> <compilation-unit> <package-root>src</package-root> <classpath mode="compile">${CLASSPATH}</classpath> //CLASSPATH is defined in build-config.properties <source-level>1.4</source-level> </compilation-unit> </java-data>
No format changes should be made for 6.0. rcauble: if you wish to use freeform projects in this way, that's up to you, but the module is not designed for such usage, so do not expect any way of disabling the Properties action/dialog to be added. The proper approach is a custom project type. (Which might, as an implementation detail, somehow delegate to the o.n.m.ant.freeform module for much of its behavior.)
*** Issue 117340 has been marked as a duplicate of this issue. ***
Changing the default component owner to tzezula.
I guess there are no plans to fix this in near future.
In fact there are no plans to fix it as freeform project is no more developed. The project.xml at least contains message <!-- Do not use Project Properties customizer when editing this file manually. --> warning about the problem. I agree with Jesse that the Project Customizer should not open or allow editing when it contains custom values.
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss