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 271102

Summary:	unloadable state isn't handled well after fix
Product:	projects	Reporter:	kalle1
Component:	Maven	Assignee:	Tomas Stupka <tstupka>
Status:	NEW ---
Severity:	normal
Priority:	P3
Version:	8.2
Hardware:	PC
OS:	Linux
Issue Type:	DEFECT	Exception Reporter:

Description kalle1 2017-07-15 10:37:20 UTC

Maven projects which contain BOMs, like https://github.com/arquillian/arquillian-showcase, cause child projects to be unloadable until a priming build fetched all dependencies and thus version numbers to allow the POMs to be valid.

After fixing the unloadable state through a successful priming build,

  * child project keep the `[name] [unloadable]` title in the project tree instead of the project name.
  * "Reload POM" has to be run for each child project and grand(grand...)child project. It should be recursive.
  * The "unloadable" state is preserved even after closing and reopening the project. A new load should retrieve up-to-date information like it would for any project which wasn't in an "unloadable" state at the first opening.

experienced with 8.2 on Ubuntu 17.04