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.

Bug 69440 - A lot of garbage output (IOExceptions) during SuitePropertiesTest
Summary: A lot of garbage output (IOExceptions) during SuitePropertiesTest
Status: CLOSED FIXED
Alias: None
Product: apisupport
Classification: Unclassified
Component: Project (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Martin Krauskopf
URL:
Keywords: TEST
Depends on:
Blocks: 173792
  Show dependency tree
 
Reported: 2005-11-28 13:29 UTC by Martin Krauskopf
Modified: 2009-10-05 19:11 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Krauskopf 2005-11-28 13:29:45 UTC
But test passes. ??
Comment 1 Martin Krauskopf 2005-11-29 11:40:56 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.
Comment 2 Martin Krauskopf 2005-11-29 15:01:26 UTC
Fixed. (Hopefully) harmfull hack.

Checking in NbModuleProject.java; 1.130 -> 1.131;
Checking in ui/customizer/SuiteUtils.java; 1.18 -> 1.19;
Comment 3 Martin Krauskopf 2005-11-29 15:04:30 UTC
Or harmless? :)
Comment 4 Tomas Danek 2005-12-12 15:54:57 UTC
closing.