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: | Customizer doesn't reload project.xml during invocations | ||
---|---|---|---|
Product: | apisupport | Reporter: | Michel Graciano <hmichel> |
Component: | Project | Assignee: | Martin Krauskopf <mkrauskopf> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | Keywords: | SIMPLEFIX |
Priority: | P2 | ||
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Michel Graciano
2005-08-07 17:35:48 UTC
1. Please file separate issue reports for separate problems. 2. Please attach instructions to reproduce your problem, since I cannot guess what exactly you are doing. Given a particular build you downloaded (name it!), and a fresh user directory, I need explicit steps I can follow to see the problem happen - describe what you observed vs. what you expected. The problem is it: When I edit my project.xml by hand, after already opened the visual project editor, the modifications are lost, because the project ui editor overwrite my modifications, but if don't occur before I open the editor. How this occur: I am developing a wrapper module, and I forgot some jars, that I add by hand these, and, some time after, I open the visual project editor, so my extra jars disappear. So, doing some tests, I restart the IDE, than I see that, if I edit my project.xml before open the editor, editor recognize my modifications. So I think that there is some cache that didn't are updated after project.xml is saved, like other project.xml for others project types, like Java Project. This occur to jars added in release/modules/ext folder, where the ant task don't copy new jars for the cluster folder. I think that it's the same problem, because I post in same issue. NetBeans version: NetBeans IDE 4.2 daily build 200508041800 Thanks for your attention and hope has answered your doubt. []'s Michel Copying of JARs from $basedir/release/ to the cluster folder is independent of the IDE's manipulation of project.xml, so there are probably two separate bugs involved. Again, if you can reproduce the problem, please provide some steps to do so; otherwise it is much less likely the bug will get fixed promptly. Follow the steps like above: 1- Open the visual project properties editor, so change any public package to true/false and press ok; 2- Open the project metadata file, than, public packages is there, than exclude some this public packages and save the file; 3- Open the visual project properties editor again, and see that the modifications in project.xml don't appear in visual editor, where appear like last time that you close this dialog. if you change any other project information, the project.xmlo file will be recreated with exclude public packages. I hope to be clear. []'s Michel Martin please evaluate... Yes, you are absolutely right. I forgot to refresh project.xml information during solving the issue 61242. Good catch! Thanks. Started Fixed. Checking in test/ui/customizer/SingleModulePropertiesTest.java; 1.10 --> 1.11 Checking in ui/customizer/SingleModuleProperties.java; 1.17 --> 1.18 v |