Done: http://jira.codehaus.org/browse/MVERSIONS-40

Cheers.

2009/5/14 Stephen Connolly <[email protected]>

> Not yet... it's an issue I have in my head
>
> If you want to raise an issue and target it for 1.0-beta-1 it would help me
> remember
>
> -Stephen
>
> 2009/5/14 Baptiste MATHUS <[email protected]>
>
> > Hi Stephen,
> >
> > Did you fix it directly in the code? Looking in the bugs for the roadmap
> of
> > the 1.0-beta1, I can't find the reference:
> >
> >
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=11830&fixfor=14766
> >
> > Does a bug report exist for this bug?
> >
> > Cheers.
> >
> > 2009/5/14 Stephen Connolly <[email protected]>
> >
> > > That will be in 1.0-beta-1
> > >
> > > 2009/5/14 DanDude <[email protected]>
> > >
> > > >
> > > > Actually, I am trying to use versions plugin to synchronize
> > dependencies
> > > > across all projects in a hierarchy, since I wish to release all
> > projects
> > > > with same version number.
> > > > update-child-modules works, but the only problem is that I have to
> > > execute
> > > > the goal on all parent poms.
> > > > Since I have a 3-level hierarchy, is tedious and error prone.
> > > > I wish I could execute update-child-modules on top parent and have it
> > > > update
> > > > all projects in the hierarchy.
> > > >
> > > >
> > > > stephenconnolly wrote:
> > > > >
> > > > > just so you know what update-child-modules does...
> > > > >
> > > > > if the child references the *wrong version of the parent* then
> > > > > update-child-modules will fix your child poms for you.
> > > > >
> > > > > it is just for fixing a broken reactor.
> > > > >
> > > > > You are probably looking for update-properties as that is really
> the
> > > only
> > > > > way (currently) to specify what dependencies to update.
> > > > >
> > > > > -Stephen
> > > > >
> > > > > 2009/5/13 DanDude <[email protected]>
> > > > >
> > > > >>
> > > > >> I have a project where my root project has child1, child2 etc...
> > Each
> > > > >> child
> > > > >> has child11, child12, child21 etc..
> > > > >> I would like to execute update-child-modules so versions across
> all
> > > > child
> > > > >> projects are updated. Is this possible?
> > > > >> --
> > > > >> View this message in context:
> > > > >>
> > > >
> > >
> >
> http://n2.nabble.com/update-child-modules-of-versions-plugin-on-the-whole-hierarchy-tp2885629p2885629.html
> > > > >> Sent from the maven users mailing list archive at Nabble.com.
> > > > >>
> > > > >>
> > > > >>
> > ---------------------------------------------------------------------
> > > > >> To unsubscribe, e-mail: [email protected]
> > > > >> For additional commands, e-mail: [email protected]
> > > > >>
> > > > >>
> > > > >
> > > > >
> > > >
> > > > --
> > > > View this message in context:
> > > >
> > >
> >
> http://n2.nabble.com/update-child-modules-of-versions-plugin-on-the-whole-hierarchy-tp2885629p2887823.html
> > > > Sent from the maven users mailing list archive at Nabble.com.
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [email protected]
> > > > For additional commands, e-mail: [email protected]
> > > >
> > > >
> > >
> >
> >
> >
> > --
> > Baptiste <Batmat> MATHUS - http://batmat.net
> > Sauvez un arbre,
> > Mangez un castor !
> >
>



-- 
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

Reply via email to