Cool, thanks :)

-Deng

On Wed, Mar 13, 2013 at 3:38 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> I thought I had included the link... But it does not seem there now...
> Strange
>
> https://github.com/stephenc/mpr-maven-plugin
>
> On Wednesday, 13 March 2013, Deng Ching-Mallete wrote:
>
> > Hi Stephen,
> >
> > Where can I get/checkout the plugin? We have a project with the same
> > structure so I'd like to try it out.
> >
> > Thanks,
> > Deng
> >
> > On Mon, Mar 11, 2013 at 7:50 PM, Stephen Connolly <
> > stephen.alan.conno...@gmail.com <javascript:;>> wrote:
> >
> > > 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
> > >
> >
> >
> >
> > --
> > Maria Odea "Deng" Ching-Mallete | och...@apache.org <javascript:;> |
> > http://www.linkedin.com/in/oching
> >
>
>
> --
> Sent from my phone
>



-- 
Maria Odea "Deng" Ching-Mallete | och...@apache.org |
http://www.linkedin.com/in/oching

Reply via email to