[ JDK VERSION : 1.6.* ]
When I choose "Open Required Projects" when opening a maven project,
not all required projects are opened. It seems that child projects
with pom packaging are not opened, although their children are.
Created attachment 88167 [details]
Maven project structure to illustrate problem
When opening the "toplevel" project of the example testcase in NB and choosing "Open Required Projects" the two child
modules subaggregator1 and subaggregator2 are not opened even though their children are.
yes, I've considered it a feature so far. In large setups, opening just the project leaves can save a bit of real estate
in the project's tab. Usually you don't want the pom packaging projects anyway, or if you do you open them manually. So
the behaviour is intentional but I'm open to discussion.
I can see your point about decluttering, but the pom projects do form part of the build and it is very useful to have
access to them. Pom packaged modules are also typically used to remove some default lifecycle bindings, for instance
when creating integration test modules. So one can have pom packaged projects containing code, etc.
I think the user should be able to choose whether or not to open the aggregated pom projects.
Reassigning to default owner.
in 8.0, Open Required projects always opens all child projects, including the pom packaged ones.