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: | A lot of garbage output (IOExceptions) during SuitePropertiesTest | ||
|---|---|---|---|
| Product: | apisupport | Reporter: | Martin Krauskopf <mkrauskopf> |
| Component: | Project | Assignee: | Martin Krauskopf <mkrauskopf> |
| Status: | CLOSED FIXED | ||
| Severity: | blocker | CC: | jglick |
| Priority: | P3 | Keywords: | TEST |
| Version: | 5.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Bug Depends on: | |||
| Bug Blocks: | 173792 | ||
|
Description
Martin Krauskopf
2005-11-28 13:29:45 UTC
Problem is that in the FileSystem.AtomicAction().run() I'm also calling AntProjectHelper.putPrimaryConfigurationData() which fires events which in few turns try to refresh ModuleList - but the project is in inconsistent state since ModuleList accesses to raw FileObject which is not yet updated (since ProjectManager.saveProject() was not saved yet). There is not probably clean straightforward solution. Probably some kind of hack will have to be involved so that we will be able to recognize that changes should be ignored (since after AtomicAction finished they will be fired again anyway). Probably the clean solution would be if the ModuleList uses AntProjectHelper.getPrimaryConfigurationData() is possible. Fixed. (Hopefully) harmfull hack. Checking in NbModuleProject.java; 1.130 -> 1.131; Checking in ui/customizer/SuiteUtils.java; 1.18 -> 1.19; Or harmless? :) closing. |