Typically, you would make each module produce a single artifact (e.g., application). The parent POM can be the multi-module POM used to build all of its modules. Any module can, itself, be an aggregator and parent of its modules so you can nest things in whatever way makes sense...
Robert Patrick <[email protected]> VP, OPC Development, Oracle Mobile: +1 469 556 9450 Sent from my iPad > On Oct 21, 2015, at 8:25 PM, Scott Klein <[email protected]> wrote: > > I am not quite sure how to ask this to make it simple, but let's say I had a > bunch of applications that wanted to share the same version via a Parent POM > - should they all be inside the same module? > > If so, what about the Parent POM, should that be inside the module too? > > I am thinking about when it comes time to release them, I am having a devil > of a time trying to make separate modules (that are inter-dependent on each > other's artifacts) release nicely using the same version. > > What is best practice? > > It seems like the way we have it setup is totally wrong, and would take a > while to explain --- which is why it is probably wrong. > >
