You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Igor Fedorenko <ig...@ifedorenko.com> on 2013/10/04 13:18:50 UTC
Re: Leaving Maven Core POMs at major.minor-SNAPSHOT
Practical question. What should be supported maven version range for new
ITs introduced during 3.1.2 development, [3.1,)? This means we'd need to
tag ITs, right? Otherwise it wouldn't be possible to successfully rerun
ITs for 3.1 and 3.1.1, unless I am mistaken.
--
Regards,
Igor
On 2013-09-14 1:24 PM, Jason van Zyl wrote:
> When a release fails like this it is annoying to have to rev back the
> version of the POM. I'm not sure who flipped the versions in the POM
> and while it's a little more visible to see what you're moving toward
> I prefer the pattern of:
>
> 3.1-SNAPSHOT --> 3.1.1 --> 3.1-SNAPSHOT --> 3.1.2 --> 3.1-SNAPSHOT
>
> I know this may not be obvious to the casual observer as they may
> think 3.1 is next, but I'm personally fine with that.
>
> Especially after a failed release because then I don't have to go
> change all the POMs (whether rolling back manually, using the release
> rollback, the version:set command, or whatever else). It's much
> easier to just fix what's necessary and carry on.
>
> Unless anyone objects I would like to go back this pattern, what I
> previously had, because it's far easier to manage. Ideally it might
> be nice if all the tools understood 3.1.z-SNAPSHOT but they don't an
> in lieu of that I would prefer not to diddle POMs after a failed
> release.
>
> Thanks,
>
> Jason
>
> ---------------------------------------------------------- Jason van
> Zyl Founder, Apache Maven http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
>
>
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Leaving Maven Core POMs at major.minor-SNAPSHOT
Posted by Hervé BOUTEMY <he...@free.fr>.
true, having this version during development does not permit core its range as
usual: an IT for a minor version will be run only at release time, but not
before and after
that's a major issue, IMHO
Regards,
Hervé
Le vendredi 4 octobre 2013 07:18:50 Igor Fedorenko a écrit :
> Practical question. What should be supported maven version range for new
> ITs introduced during 3.1.2 development, [3.1,)? This means we'd need to
> tag ITs, right? Otherwise it wouldn't be possible to successfully rerun
> ITs for 3.1 and 3.1.1, unless I am mistaken.
>
> --
> Regards,
> Igor
>
> On 2013-09-14 1:24 PM, Jason van Zyl wrote:
> > When a release fails like this it is annoying to have to rev back the
> > version of the POM. I'm not sure who flipped the versions in the POM
> > and while it's a little more visible to see what you're moving toward
> > I prefer the pattern of:
> >
> > 3.1-SNAPSHOT --> 3.1.1 --> 3.1-SNAPSHOT --> 3.1.2 --> 3.1-SNAPSHOT
> >
> > I know this may not be obvious to the casual observer as they may
> > think 3.1 is next, but I'm personally fine with that.
> >
> > Especially after a failed release because then I don't have to go
> > change all the POMs (whether rolling back manually, using the release
> > rollback, the version:set command, or whatever else). It's much
> > easier to just fix what's necessary and carry on.
> >
> > Unless anyone objects I would like to go back this pattern, what I
> > previously had, because it's far easier to manage. Ideally it might
> > be nice if all the tools understood 3.1.z-SNAPSHOT but they don't an
> > in lieu of that I would prefer not to diddle POMs after a failed
> > release.
> >
> > Thanks,
> >
> > Jason
> >
> > ---------------------------------------------------------- Jason van
> > Zyl Founder, Apache Maven http://twitter.com/jvanzyl
> > ---------------------------------------------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Leaving Maven Core POMs at major.minor-SNAPSHOT
Posted by Jason van Zyl <ja...@tesla.io>.
Good point. I did some experiments with the version:set plugin and I can live with the rollback using that. So I reset the poms to 3.1.2-SNAPSHOT. Problem solved.
On Oct 4, 2013, at 7:18 AM, Igor Fedorenko <ig...@ifedorenko.com> wrote:
> Practical question. What should be supported maven version range for new
> ITs introduced during 3.1.2 development, [3.1,)? This means we'd need to
> tag ITs, right? Otherwise it wouldn't be possible to successfully rerun
> ITs for 3.1 and 3.1.1, unless I am mistaken.
>
> --
> Regards,
> Igor
>
> On 2013-09-14 1:24 PM, Jason van Zyl wrote:
>> When a release fails like this it is annoying to have to rev back the
>> version of the POM. I'm not sure who flipped the versions in the POM
>> and while it's a little more visible to see what you're moving toward
>> I prefer the pattern of:
>>
>> 3.1-SNAPSHOT --> 3.1.1 --> 3.1-SNAPSHOT --> 3.1.2 --> 3.1-SNAPSHOT
>>
>> I know this may not be obvious to the casual observer as they may
>> think 3.1 is next, but I'm personally fine with that.
>>
>> Especially after a failed release because then I don't have to go
>> change all the POMs (whether rolling back manually, using the release
>> rollback, the version:set command, or whatever else). It's much
>> easier to just fix what's necessary and carry on.
>>
>> Unless anyone objects I would like to go back this pattern, what I
>> previously had, because it's far easier to manage. Ideally it might
>> be nice if all the tools understood 3.1.z-SNAPSHOT but they don't an
>> in lieu of that I would prefer not to diddle POMs after a failed
>> release.
>>
>> Thanks,
>>
>> Jason
>>
>> ---------------------------------------------------------- Jason van
>> Zyl Founder, Apache Maven http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>>
>>
>>
>>
>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
Re: Leaving Maven Core POMs at major.minor-SNAPSHOT
Posted by Robert Scholte <rf...@apache.org>.
Good catch!
Op Fri, 04 Oct 2013 13:18:50 +0200 schreef Igor Fedorenko
<ig...@ifedorenko.com>:
> Practical question. What should be supported maven version range for new
> ITs introduced during 3.1.2 development, [3.1,)? This means we'd need to
> tag ITs, right? Otherwise it wouldn't be possible to successfully rerun
> ITs for 3.1 and 3.1.1, unless I am mistaken.
>
> --
> Regards,
> Igor
>
> On 2013-09-14 1:24 PM, Jason van Zyl wrote:
>> When a release fails like this it is annoying to have to rev back the
>> version of the POM. I'm not sure who flipped the versions in the POM
>> and while it's a little more visible to see what you're moving toward
>> I prefer the pattern of:
>>
>> 3.1-SNAPSHOT --> 3.1.1 --> 3.1-SNAPSHOT --> 3.1.2 --> 3.1-SNAPSHOT
>>
>> I know this may not be obvious to the casual observer as they may
>> think 3.1 is next, but I'm personally fine with that.
>>
>> Especially after a failed release because then I don't have to go
>> change all the POMs (whether rolling back manually, using the release
>> rollback, the version:set command, or whatever else). It's much
>> easier to just fix what's necessary and carry on.
>>
>> Unless anyone objects I would like to go back this pattern, what I
>> previously had, because it's far easier to manage. Ideally it might
>> be nice if all the tools understood 3.1.z-SNAPSHOT but they don't an
>> in lieu of that I would prefer not to diddle POMs after a failed
>> release.
>>
>> Thanks,
>>
>> Jason
>>
>> ---------------------------------------------------------- Jason van
>> Zyl Founder, Apache Maven http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>>
>>
>>
>>
>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org