Hi,
On Thu, Nov 18, 2010 at 5:26 PM, Marshall Schor <[email protected]> wrote:
> After some iterations and discussions with colleagues, here's the next
> "improvement" which I think will fix these problems. The main idea is to make
> the "main" aggregator project for each multi-module build (e.g., the "uimaj"
> project for the uimaj SDK) also be a parent-pom for all those modules in the
> multi-module build, as is conventional Maven practice.
There are cases where you may want to put things in the aggregator POM
that you don't want inherited by other modules. To avoid that problem
I'd recommend adding a separate parent module to the build. For
example, in Jackrabbit our build structure is:
org.apache.jackrabbit:jackrabbit (the aggregator)
+-- :jackrabbit-parent (the parent)
+-- :jackrabbit-api
+-- :jackrabbit-jcr-commons
...
All modules, including the aggregator, inherit the included parent
POM. That parent POM on the other hand inherits another project-wide
POM (that then inherits the org.apache:apache POM...) that we maintain
and release separately pretty much like you described.
BR,
Jukka Zitting
