Well with my Maven hat on, I don't like that it requires Jenkins nor that it is (most likely from a quick look) using the (IMPO fundamentally broken) Maven Project type for jobs
But in essence I envision a Maven plugin with a similar end-goal... just not yet confident enough of my logic for detecting downstream projects. I think my logic for detecting release roots is sound though. (although it probably fails for some of the maven plugins @ asf as they can inherit their SCM even though they are released independently... might be worth checking for some other explicit markers) On 11 March 2013 14:18, Andrei Pozolotin <[email protected]> wrote: > * Stephen** > * > I made this solution for the problem: > https://github.com/barchart/barchart-jenkins-cascade-plugin/wiki > > Please let me know what you think? > > Thank you, > > Andrei > > -------- Original Message -------- > Subject: Multi-project releases > From: Stephen Connolly > <[email protected]><[email protected]> > To: Maven Developers List <[email protected]> <[email protected]> > Date: Mon 11 Mar 2013 06:50:38 AM CDT > > 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 > > > >
