Brain Dump 3

[Stephen Connolly] (http://mail-archives.apache.org/mod_mbox/maven-dev/201303.mbox/%3CCA+nPnMzzLCGrxrW72OVKLh2ZAFphn7dh1yfz7TDiGX8wD5-maw@mail.gmail.com%3E )

Hey one and all,

So we all know how multiple projects with multiple release roots are a
pain...

Here's some experiments I've been playing with...

Not yet brave enough to have it fire up release:prepare release:perform on
each release root, nor fire up versions:set on the downstream projects with
explicit dependencies, nor lather rinse repeat until there is nothing
needing a release...

But even the simple report should be useful, and if anyone has suggestions
to help improve its recommendations towards getting confidence that the
automated stuff could work... please give me pull requests.

If this proves useful, I will probably roll it into the release plugin...
but for now I'll keep it in a holding pattern on github (where it is not in
a default plugin groupId and hence relocation is less of an issue if I do
happen to make any releases into central)

$ mvn com.github.stephenc.maven:mpr-maven-plugin:list-roots

from an aggregator pom should identify all the release roots and whether
they might need a release

-Stephen