|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Display Modes |
|
#1
|
|||
|
|||
|
Proper Dependency Management - HowTo?
11) don't mix inheritance and aggregation. that means a parent pom NEVER
ever has modules, if you think about the concept for a minute - or longer - there will be a moment of enlightenment > > structure of the generated archetype. > So, I'm curious as to why you would say not to do this. > Yeah, me too! First, I had a parent pom, and a "all-projects-pom" which was just and only a multimodule pom. But then you had even one more pom, and we decided to put the multimodule stuff right into the parent pom. using the "-N" flag allows to simply work (package, install, deploy, site) with the parent pom, while without you may easily work(package, install, deploy, site) on all projects at once. Thanks, Peter |
![]() |
| Viewing: Web Development Archives > Mailing Lists > Java > Proper Dependency Management - HowTo? |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|