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.
Detected while trying to fix issue #57480. If a UQE is thrown while trying to write out a new project.xml, the ProjectXmlSavedHook must be called *after* the user agrees to edit project.xml and new content is written, rather than within the dynamic scope of ProjectManager.saveProject. Otherwise, an impl (such as using GeneratedFilesHelper) will see the old project.xml, which can cause it to behave incorrectly, e.g. not regenerating build-impl.xml with new content.
Have patch. Ugly but seems to work.
See commit log in #57791.
Need QA assistance.
Jesse, what is the manifestation of this bug for user? In other words how can I reproduce it?
I am going to verify this together with issue #57480.
I have tried hard but couldn't reproduce the deadlock in continuous trunk build #20050413-0713 of NetBeans 4.2. I agree with integration to release41 branch.
"I have tried hard but couldn't reproduce the deadlock" - this isn't a deadlock! Typo? User effect: well if the fix for #57480 goes in, it will still not make build-impl.xml be modified after e.g. adding a new subproject, so the build will fail. It is because build-impl.xml is regenerated - but *before* the modified project.xml is written to disk (since the user might not yet have agreed to issue the edit command for project.xml).
Yes, sorry. Copy&paste error in a hurry. What I meant is that *.xml files were correctly updated i.e. project could be run without problems.
I guess I'll consider that verified.
Merged w/ issue #57791.