Question regarding inheritance vs pluginManagement

Hi, I was refactoring my projects to make better use of dependency management and pluginManagement. Almost got it all to work the way I want but I hit a wall in how the pluginManagement is used. When looking at the definition in the documentation find the following *pluginManagement: is an

Re: Question regarding inheritance vs pluginManagement

Thanks for answering and clarify the documentation. I also looked into profiles and it looked quite promising but limitations on how they are activated and inherited let me to (yet another) dead end. This however leaves me hung dry... how else can I obtain the desired functionality (modulate

POM element orders

Hello, I'm having a bit of a problem here ! I have a project that while not very big, does span a dependency tree a few level deep and has many leaves of final deployed packages. I use maven not only to build and all but to generate zip files that contain everything (doc, runtime environment,

Re: POM element orders

Thanks Justin, sounds reasonable... there are so many phases to choose from I guess the expanding of the package could very well be in the pre-package phase. @Brian.. That`s just it, when I put the assembly bits in the parent POM it is systematically executed before anything in the children`s

Re: multi-module unit testing

Hi Pierre, It all depends on what you need to share. I discovered that a lot of the code I needed to share were things like data set loaders for specification tests for example. These are generic by nature and do not require any dependencies, thus making isolation in a separate module pretty

Re: custom jar contents?

Simple answer : If you need two jars then your project needs to be broken into two separate projects. To get a better understanding I would like to know why you require to have two jars ? different configurations ? optional components ? Believe me here I got through this a while ago on Maven

Re: multi-module unit testing

Hi Pierre, The way I solved this for myself was to create a test project and put all the common test code in it (as normal stuff, not as test stuff) then I used the test project in all other projects as a dependency. This way I have access to the common test stuff. then to ensure that the extra