You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Ulrich Stärk <ul...@spielviel.de> on 2012/10/26 14:33:14 UTC
publishing snapshot artifacts
Publishing snapshot artifcats from CI builds is working again. We now have to give the Jenkins job
the version that we want it to use, at the moment this is 5.4-SNAPSHOT. This means that we have to
modify (and don't forget to) the Jenkins job every time we bump version numbers. I'm not happy with
this as I know that we'll forget and CI and snapshots will stop working again.
I don't know when we started this but we should go back to our previous process of leaving the
version at 5.x-SNAPSHOT and only during the release or a preview release fix the version number for
that release at 5.x-alpha-y or 5.x.y or whatever.
Uli
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: publishing snapshot artifacts
Posted by Howard Lewis Ship <hl...@gmail.com>.
On Friday, October 26, 2012, Ulrich Stärk wrote:
> It's not about 5.x-SNAPSHOT vs. 5.4-SNAPSHOT but rather about whether to
> put the version number to
> use in build.gradle or the Jenkins job definition. I believe that it
> belongs in the first and not in
> the latter and that final versions should only be set during the release.
>
> Uli
>
> On 26.10.2012 14:41, Bob Harner wrote:
> > Thank you, Uli!
> >
> > I don't see any reason not to use 5.x-SNAPSHOT rather than
> > 5.4-SNAPSHOT. It really means the same thing.
> >
> > On Fri, Oct 26, 2012 at 8:33 AM, Ulrich Stärk <uli@spielviel.de<javascript:;>>
> wrote:
> >> Publishing snapshot artifcats from CI builds is working again. We now
> have to give the Jenkins job
> >> the version that we want it to use, at the moment this is 5.4-SNAPSHOT.
> This means that we have to
> >> modify (and don't forget to) the Jenkins job every time we bump version
> numbers. I'm not happy with
> >> this as I know that we'll forget and CI and snapshots will stop working
> again.
> >>
> >> I don't know when we started this but we should go back to our previous
> process of leaving the
> >> version at 5.x-SNAPSHOT and only during the release or a preview
> release fix the version number for
> >> that release at 5.x-alpha-y or 5.x.y or whatever
+1
>
>>
> >> Uli
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org<javascript:;>
> >> For additional commands, e-mail: dev-help@tapestry.apache.org<javascript:;>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org<javascript:;>
> > For additional commands, e-mail: dev-help@tapestry.apache.org<javascript:;>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org <javascript:;>
> For additional commands, e-mail: dev-help@tapestry.apache.org<javascript:;>
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
Re: publishing snapshot artifacts
Posted by Ulrich Stärk <ul...@spielviel.de>.
It's not about 5.x-SNAPSHOT vs. 5.4-SNAPSHOT but rather about whether to put the version number to
use in build.gradle or the Jenkins job definition. I believe that it belongs in the first and not in
the latter and that final versions should only be set during the release.
Uli
On 26.10.2012 14:41, Bob Harner wrote:
> Thank you, Uli!
>
> I don't see any reason not to use 5.x-SNAPSHOT rather than
> 5.4-SNAPSHOT. It really means the same thing.
>
> On Fri, Oct 26, 2012 at 8:33 AM, Ulrich Stärk <ul...@spielviel.de> wrote:
>> Publishing snapshot artifcats from CI builds is working again. We now have to give the Jenkins job
>> the version that we want it to use, at the moment this is 5.4-SNAPSHOT. This means that we have to
>> modify (and don't forget to) the Jenkins job every time we bump version numbers. I'm not happy with
>> this as I know that we'll forget and CI and snapshots will stop working again.
>>
>> I don't know when we started this but we should go back to our previous process of leaving the
>> version at 5.x-SNAPSHOT and only during the release or a preview release fix the version number for
>> that release at 5.x-alpha-y or 5.x.y or whatever.
>>
>> Uli
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: publishing snapshot artifacts
Posted by Bob Harner <bo...@gmail.com>.
Thank you, Uli!
I don't see any reason not to use 5.x-SNAPSHOT rather than
5.4-SNAPSHOT. It really means the same thing.
On Fri, Oct 26, 2012 at 8:33 AM, Ulrich Stärk <ul...@spielviel.de> wrote:
> Publishing snapshot artifcats from CI builds is working again. We now have to give the Jenkins job
> the version that we want it to use, at the moment this is 5.4-SNAPSHOT. This means that we have to
> modify (and don't forget to) the Jenkins job every time we bump version numbers. I'm not happy with
> this as I know that we'll forget and CI and snapshots will stop working again.
>
> I don't know when we started this but we should go back to our previous process of leaving the
> version at 5.x-SNAPSHOT and only during the release or a preview release fix the version number for
> that release at 5.x-alpha-y or 5.x.y or whatever.
>
> Uli
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org