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: | Module suite properties dialog modifies files needlessly | ||
|---|---|---|---|
| Product: | third-party | Reporter: | Nathan Fiedler <nlfiedler> |
| Component: | -- Other -- | Assignee: | issues@third-party <issues> |
| Status: | NEW --- | ||
| Severity: | blocker | ||
| Priority: | P3 | ||
| Version: | 5.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
This problem was fixed #63346 on NetBeans side. JSwat Debugger ? |
Using NB 5.5 beta 2 on Windows XP with Subversion 1.2.3 (but not the Subversion plugin, just command-line). I have a module suite project containing a collection of module projects. I have set up the branding files under the directory named "branding", including these files: branding\core\core.jar\org\netbeans\core\startup\Bundle.properties branding\modules\org-netbeans-core.jar\org\netbeans\core\ui\Bundle.properties branding\modules\org-netbeans-core-windows.jar\org\netbeans\core\windows\view\ui\Bundle.properties To start with, the revision control system says these files are clean and up-to-date. Now say I bring up the module suite Properties dialog and immediately click the Ok button, without changing anything -- now those three aforementioned files are modified. They have been completely rewritten, and the currentVersion property has been modified to "JSwat Debugger {0}". I had specifically hand-edited that property to not include the {0}, so I then have to edit it again to correct the problem. Note that this happens just the first time. If I leave the IDE open and revert those files and bring up the module suite Properties dialog again, the files are not modified. Also note, it would be great if I could edit that currentVersion property properly using the Properties dialog. It is annoying that I must hand-edit the file to get the result that I want.