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.
I created some J2SE projects in Netbeans 5.0. When opening the projects in Netbeans 6.0, the project files in the nbproject directories are converted according to the 6.0 conventions automatically. The changes are not bad, but Netbeans shouldn't be allowed to change the files without the possibility of user intervention. At least there should be a warning before the changes are made, allowing the user to bale out, similar to the upgrade from 4.0 to 5.0.
*** Issue 116483 has been marked as a duplicate of this issue. ***
The changes from NB 5.x to NB 6.0 are compatible unlike the changes from NB 4.x to 5.0. These changes do not harm the project, the project still works in NB 5.x. unlike the project from 5.x in 4.x. When the IDE tries to do any noncompatible changes it warns you about it.
I agree that the changes do not harm the project, but the mere fact that a program changes files without my explicit permission worries me. I only noticed the change because I use Subversion. Just wanted to see how NB 6 is doing (very nice indeed!), and noticed that somewhere in the project were some uncommitted files. It would be nice to get a notification at least, with a text not to worry about the changes since they are compatible with NB 5
OK, makes sense. The only question is if it should be a modal dialog like in case of incompatible change or if it should be some kind of "softer" warning. Adding UI to cc list.
I don't know. We don't generally display a dialog every time we make a compatible format upgrade in a project, e.g. just because we fixed a bug in build-impl.xml. Do we really want such a dialog to appear? Would it cause more alarm than reassurance?
The changes in the build-impl.xml aren't important and shouldn't be notified, the question is if we should notify the compatible changes in project.properties. The dialog is probably worse than nothing, user needs to click the OK button, maybe some message in th status line when the project is opened.
moving opened issues from TM <= 6.1 to TM=Dev