Please use the Apache issue tracking system for new NetBeans issues (https://issues.apache.org/jira/projects/NETBEANS0/issues) !!
Bug 172849 - [68cat] Child POM projects not considered "required projects"
[68cat] Child POM projects not considered "required projects"
Status: RESOLVED FIXED
Product: projects
Classification: Unclassified
Component: Maven
6.x
All All
: P4 (vote)
: 8.0
Assigned To: Milos Kleint
issues@platform
:
Depends on: 210465
Blocks:
  Show dependency treegraph
 
Reported: 2009-09-23 10:24 UTC by neilg
Modified: 2014-01-02 15:20 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
:


Attachments
Maven project structure to illustrate problem (18.27 KB, application/x-compressed)
2009-09-23 10:28 UTC, neilg
Details

Note You need to log in before you can comment on or make changes to this bug.
Description neilg 2009-09-23 10:24:37 UTC
[ 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.
Comment 1 neilg 2009-09-23 10:28:58 UTC
Created attachment 88167 [details]
Maven project structure to illustrate problem
Comment 2 neilg 2009-09-23 10:31:15 UTC
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.
Comment 3 Milos Kleint 2009-09-23 11:56:52 UTC
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.
Comment 4 neilg 2009-09-25 10:38:19 UTC
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.
Comment 5 Antonin Nebuzelsky 2010-07-30 15:17:33 UTC
Reassigning to default owner.
Comment 6 Milos Kleint 2014-01-02 15:20:00 UTC
in 8.0, Open Required projects always opens all child projects, including the pom packaged ones.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo