Thanks Jeff ! I think we should try it next time which should be soon in a
Milestone cycle.
 Le 18 juil. 2013 00:31, "Jeff MAURY" <jeffma...@jeffmaury.com> a écrit :

> The release plugin has a pushChanges flag for git which is true by default
> for preserving compatibility but could be useful.
>
> Jeff
>
>
> On Thu, Jul 18, 2013 at 12:26 AM, sebb <seb...@gmail.com> wrote:
>
> > On 17 July 2013 23:19, Julien Vermillard <jvermill...@gmail.com> wrote:
> > > I think the main problem is maven release is pushing your modification
> > > when it could do all the work locally.
> >
> > It's not possible to do it all locally. It must at least commit the
> > tag to be used for the release vote.
> >
> > > perhaps we can configure that ?
> >
> > Good luck; I suspect this is buried deep within an undocumented plugin.
> >
> > > --
> > > Julien Vermillard :::: http://people.apache.org/~jvermillard/
> > >
> > >
> > > On Thu, Jul 18, 2013 at 12:07 AM, sebb <seb...@gmail.com> wrote:
> > >> On 17 July 2013 17:44, Emmanuel Lécharny <elecha...@gmail.com> wrote:
> > >>> Le 7/17/13 6:15 PM, sebb a écrit :
> > >>>> On 17 July 2013 17:00, Emmanuel Lécharny <elecha...@gmail.com>
> wrote:
> > >>>>> Le 7/17/13 5:53 PM, sebb a écrit :
> > >>>>>> On 17 July 2013 15:19, Emmanuel Lécharny <elecha...@gmail.com>
> > wrote:
> > >>>>>> With SVN the way I do it is:
> > >>>>> We don't use SVN anymore.
> > >>>> I realise that.
> > >>>>
> > >>>> Maybe Git offers functionality that would allow a similar approach
> > >>>> which achieves the same goals:
> > >>>> - don't leave trunk in a temporary state even for a short period
> > >>>> - make respins easier
> > >>>> - don't update trunk until actually ready to move to the next
> > >>>> development version
> > >>>
> > >>> This is why I proposed to create a temporary branch for the on-going
> > >>> release, leaving the trunk as is.
> > >>>
> > >>> I don't know how easy it is to do that with Maven.
> > >>
> > >> Maven can in theory do whatever the underlying SCM allows.
> > >> Whether the Maven project will agree to make the changes is another
> > matter.
> > >>
> > >> More to the point - does Git offer similar functionality to SVN for
> > >> this purpose?
> > >> I have no experience of Git, so I have no idea how to do it.
> > >>
> > >>> --
> > >>> Regards,
> > >>> Cordialement,
> > >>> Emmanuel Lécharny
> > >>> www.iktek.com
> > >>>
> >
>
>
>
> --
> Jeff MAURY
>
>
> "Legacy code" often differs from its suggested alternative by actually
> working and scaling.
>  - Bjarne Stroustrup
>
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.com
> http://www.twitter.com/jeffmaury
>

Reply via email to