I'm not a maven expert, so others may chime in with corrections/ improvements 
:-)

Here's how I think about this.

First, I separate out the idea of "parent" and "aggregator", using "parent" to
denote POMs that factor out common settings from their children, and using
"aggregator" to denote POMs that have a <modules> element, specifying
sub-projects to build together.

In fact, these can be entirely separate POMs - since they're for different 
purposes.
You could, even, have several different "aggregator" projects, over the same set
of sub-modules, if that made sense.

Then, for releasing, you have a choice:

1) release one (sub) project by itself
2) release several (sub) projects together
3) use an "aggregator" project to release several projects together.

So, in your case, you could release the aggregator project at level 1.0, and
then, if you no longer desired to have all the sub-projects at the same level
(as you seem to indicate), you could subsequently release just the child-web
project.

There could be potentially some difference in the builds done by default for an
aggregator project versus doing an individual sub-project build.  For instance,
a common practice is to have the "top-most" project (the aggregator, for
instance), do a consolidated source-release zip packaging over all the
submodules.  If you built just one project, that project would, of course, have
its own source-release zip package.

So, I think it's up to you, how you want to manage this. 

Does this make sense?  Or am I missing the main point?

-Marshall Schor

On 9/29/2010 4:29 PM, Nathaniel Auvil wrote:
> I am trying to figure out how to leverage mult-module builds in maven. Say i
> have a project defined as:
>
> parent
> child-core
> child-service
> child-web
>
> where both child-service and child-web are dependent on child-core
>
>
> ok. i do a first release and everything is at version 1.0 as in:
> parent (1.0)
> child-core (1.0)
> child-service (1.0)
> child-web (1.0)
>
>
> Some days later there is a bug in the child-web project. What i _want_ is...
>
> parent (1.1)
> child-core (1.0)
> child-service (1.0)
> child-web (1.1)
>
> how can i do this with maven?
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to