2.3.0-incubating-SNAPSHOT

[Thilo Goetz <tw...@gmx.de>]

Somebody please remind me: what's the purpose of the
-SNAPSHOT version name?  Doesn't this just mean that
every POM needs to updated twice for a new version,
once with the snapshot tag, and once without?
Why aren't we going to the next version directly?
It's not like we're publishing snapshot releases.

--Thilo

Re: 2.3.0-incubating-SNAPSHOT

[Tommaso Teofili <to...@gmail.com>]

2009/6/16 LeHouillier, Frank D. <Fr...@gd-ais.com>

> No, but you should look at the maven release plugin for handling the
> change from 2.n-SNAPSHOT in (trunk) to 2.n (in tags) to 2.n+1-SNAPSHOT
> (back in trunk).  It should handle all of the SNAPSHOT dependencies
> automatically rather than doing this by hand.  As it stands now, are you
> planning to change all the versions to 2.3.1-incubating-SNAPSHOT after
> the release of 2.3.1-incubating?  In general, I agree with Jukka, that
> if I have a dependency that isn't labeled SNAPSHOT, I trust this version
> not to change.  Since we do sometimes build UIMA trunk internally, this
> won't be the case if SNAPSHOT is abandoned forever.


I do agree



>
>
> -----Original Message-----
> From: Thilo Goetz [mailto:twgoetz@gmx.de]
> Sent: Tuesday, June 16, 2009 10:12 AM
> To: uima-dev@incubator.apache.org
> Subject: Re: 2.3.0-incubating-SNAPSHOT
>
> Jukka Zitting wrote:
> > Hi,
> >
> > On Tue, Jun 16, 2009 at 3:40 PM, Thilo Goetz<tw...@gmx.de> wrote:
> >> I guess I'm just displaying my maven ignorance here.  Since
> >> we're not uploading any snapshot artifacts to any maven
> >> repos, does it still buy us anything?
> >
> > It does. If I build UIMA today, I get a SNAPSHOT version in my local
> > Maven repository instead of a version that may later interfere with
> > the final release.
> >
> > A SNAPSHOT can change from day to day, but a release version should
> > always stay the same.
>
> Ok, by all means.  Still, since the version number needs
> to be updated in a gazillion places, and I've already made
> a start, anybody object to me changing the version number
> to 2.3.0-incubating (no snapshot) now, so we can catch all
> the places that I'm sure to have missed until we finally
> release?
>
> --Thilo
>
>
>
> >
> > BR,
> >
> > Jukka Zitting
>

Re: 2.3.0-incubating-SNAPSHOT

[Thilo Goetz <tw...@gmx.de>]

Tommaso Teofili wrote:
> 2009/6/16 Thilo Goetz <tw...@gmx.de>
> 
>> LeHouillier, Frank D. wrote:
>>> No, but you should look at the maven release plugin for handling the
>>> change from 2.n-SNAPSHOT in (trunk) to 2.n (in tags) to 2.n+1-SNAPSHOT
>>> (back in trunk).  It should handle all of the SNAPSHOT dependencies
>>> automatically rather than doing this by hand.  As it stands now, are you
>> Do I hear you volunteer?
>>
>>> planning to change all the versions to 2.3.1-incubating-SNAPSHOT after
>>> the release of 2.3.1-incubating?  In general, I agree with Jukka, that
>>> if I have a dependency that isn't labeled SNAPSHOT, I trust this version
>>> not to change.  Since we do sometimes build UIMA trunk internally, this
>>> won't be the case if SNAPSHOT is abandoned forever.
>> I don't think we'll abandon snapshot release numbering, I understand
>> the need for it now.  However, we do need a better way to maintain
>> the version numbers in the various places we have.  I don't have and
>> am not planning on acquiring the maven skill to improve the situation.
>> So help in that quarter would be appreciated.
> 
> 
> An idea could be to define a UIMA super POM, a parent POM in which you
> deploy properties common to all modules, if you'd like one point in which
> handle common properties, this can be a good practice.
> Tommaso

We have that, actually.  We're not using it to manage the dependencies,
though.

--Thilo

Re: 2.3.0-incubating-SNAPSHOT

[Tommaso Teofili <to...@gmail.com>]

2009/6/16 Thilo Goetz <tw...@gmx.de>

> LeHouillier, Frank D. wrote:
> > No, but you should look at the maven release plugin for handling the
> > change from 2.n-SNAPSHOT in (trunk) to 2.n (in tags) to 2.n+1-SNAPSHOT
> > (back in trunk).  It should handle all of the SNAPSHOT dependencies
> > automatically rather than doing this by hand.  As it stands now, are you
>
> Do I hear you volunteer?
>
> > planning to change all the versions to 2.3.1-incubating-SNAPSHOT after
> > the release of 2.3.1-incubating?  In general, I agree with Jukka, that
> > if I have a dependency that isn't labeled SNAPSHOT, I trust this version
> > not to change.  Since we do sometimes build UIMA trunk internally, this
> > won't be the case if SNAPSHOT is abandoned forever.
>
> I don't think we'll abandon snapshot release numbering, I understand
> the need for it now.  However, we do need a better way to maintain
> the version numbers in the various places we have.  I don't have and
> am not planning on acquiring the maven skill to improve the situation.
> So help in that quarter would be appreciated.


An idea could be to define a UIMA super POM, a parent POM in which you
deploy properties common to all modules, if you'd like one point in which
handle common properties, this can be a good practice.
Tommaso



>
>
> --Thilo
>
> >
> > -----Original Message-----
> > From: Thilo Goetz [mailto:twgoetz@gmx.de]
> > Sent: Tuesday, June 16, 2009 10:12 AM
> > To: uima-dev@incubator.apache.org
> > Subject: Re: 2.3.0-incubating-SNAPSHOT
> >
> > Jukka Zitting wrote:
> >> Hi,
> >>
> >> On Tue, Jun 16, 2009 at 3:40 PM, Thilo Goetz<tw...@gmx.de> wrote:
> >>> I guess I'm just displaying my maven ignorance here.  Since
> >>> we're not uploading any snapshot artifacts to any maven
> >>> repos, does it still buy us anything?
> >> It does. If I build UIMA today, I get a SNAPSHOT version in my local
> >> Maven repository instead of a version that may later interfere with
> >> the final release.
> >>
> >> A SNAPSHOT can change from day to day, but a release version should
> >> always stay the same.
> >
> > Ok, by all means.  Still, since the version number needs
> > to be updated in a gazillion places, and I've already made
> > a start, anybody object to me changing the version number
> > to 2.3.0-incubating (no snapshot) now, so we can catch all
> > the places that I'm sure to have missed until we finally
> > release?
> >
> > --Thilo
> >
> >
> >
> >> BR,
> >>
> >> Jukka Zitting
>

Re: 2.3.0-incubating-SNAPSHOT

[Thilo Goetz <tw...@gmx.de>]

LeHouillier, Frank D. wrote:
> No, but you should look at the maven release plugin for handling the
> change from 2.n-SNAPSHOT in (trunk) to 2.n (in tags) to 2.n+1-SNAPSHOT
> (back in trunk).  It should handle all of the SNAPSHOT dependencies
> automatically rather than doing this by hand.  As it stands now, are you

Do I hear you volunteer?

> planning to change all the versions to 2.3.1-incubating-SNAPSHOT after
> the release of 2.3.1-incubating?  In general, I agree with Jukka, that
> if I have a dependency that isn't labeled SNAPSHOT, I trust this version
> not to change.  Since we do sometimes build UIMA trunk internally, this
> won't be the case if SNAPSHOT is abandoned forever.

I don't think we'll abandon snapshot release numbering, I understand
the need for it now.  However, we do need a better way to maintain
the version numbers in the various places we have.  I don't have and
am not planning on acquiring the maven skill to improve the situation.
So help in that quarter would be appreciated.

--Thilo

> 
> -----Original Message-----
> From: Thilo Goetz [mailto:twgoetz@gmx.de] 
> Sent: Tuesday, June 16, 2009 10:12 AM
> To: uima-dev@incubator.apache.org
> Subject: Re: 2.3.0-incubating-SNAPSHOT
> 
> Jukka Zitting wrote:
>> Hi,
>>
>> On Tue, Jun 16, 2009 at 3:40 PM, Thilo Goetz<tw...@gmx.de> wrote:
>>> I guess I'm just displaying my maven ignorance here.  Since
>>> we're not uploading any snapshot artifacts to any maven
>>> repos, does it still buy us anything?
>> It does. If I build UIMA today, I get a SNAPSHOT version in my local
>> Maven repository instead of a version that may later interfere with
>> the final release.
>>
>> A SNAPSHOT can change from day to day, but a release version should
>> always stay the same.
> 
> Ok, by all means.  Still, since the version number needs
> to be updated in a gazillion places, and I've already made
> a start, anybody object to me changing the version number
> to 2.3.0-incubating (no snapshot) now, so we can catch all
> the places that I'm sure to have missed until we finally
> release?
> 
> --Thilo
> 
> 
> 
>> BR,
>>
>> Jukka Zitting

RE: 2.3.0-incubating-SNAPSHOT

["LeHouillier, Frank D." <Fr...@gd-ais.com>]

No, but you should look at the maven release plugin for handling the
change from 2.n-SNAPSHOT in (trunk) to 2.n (in tags) to 2.n+1-SNAPSHOT
(back in trunk).  It should handle all of the SNAPSHOT dependencies
automatically rather than doing this by hand.  As it stands now, are you
planning to change all the versions to 2.3.1-incubating-SNAPSHOT after
the release of 2.3.1-incubating?  In general, I agree with Jukka, that
if I have a dependency that isn't labeled SNAPSHOT, I trust this version
not to change.  Since we do sometimes build UIMA trunk internally, this
won't be the case if SNAPSHOT is abandoned forever.

-----Original Message-----
From: Thilo Goetz [mailto:twgoetz@gmx.de] 
Sent: Tuesday, June 16, 2009 10:12 AM
To: uima-dev@incubator.apache.org
Subject: Re: 2.3.0-incubating-SNAPSHOT

Jukka Zitting wrote:
> Hi,
> 
> On Tue, Jun 16, 2009 at 3:40 PM, Thilo Goetz<tw...@gmx.de> wrote:
>> I guess I'm just displaying my maven ignorance here.  Since
>> we're not uploading any snapshot artifacts to any maven
>> repos, does it still buy us anything?
> 
> It does. If I build UIMA today, I get a SNAPSHOT version in my local
> Maven repository instead of a version that may later interfere with
> the final release.
> 
> A SNAPSHOT can change from day to day, but a release version should
> always stay the same.

Ok, by all means.  Still, since the version number needs
to be updated in a gazillion places, and I've already made
a start, anybody object to me changing the version number
to 2.3.0-incubating (no snapshot) now, so we can catch all
the places that I'm sure to have missed until we finally
release?

--Thilo



> 
> BR,
> 
> Jukka Zitting

Re: 2.3.0-incubating-SNAPSHOT

[Thilo Goetz <tw...@gmx.de>]

Jukka Zitting wrote:
> Hi,
> 
> On Tue, Jun 16, 2009 at 3:40 PM, Thilo Goetz<tw...@gmx.de> wrote:
>> I guess I'm just displaying my maven ignorance here.  Since
>> we're not uploading any snapshot artifacts to any maven
>> repos, does it still buy us anything?
> 
> It does. If I build UIMA today, I get a SNAPSHOT version in my local
> Maven repository instead of a version that may later interfere with
> the final release.
> 
> A SNAPSHOT can change from day to day, but a release version should
> always stay the same.

Ok, by all means.  Still, since the version number needs
to be updated in a gazillion places, and I've already made
a start, anybody object to me changing the version number
to 2.3.0-incubating (no snapshot) now, so we can catch all
the places that I'm sure to have missed until we finally
release?

--Thilo



> 
> BR,
> 
> Jukka Zitting

Re: 2.3.0-incubating-SNAPSHOT

[Jukka Zitting <ju...@gmail.com>]

Hi,

On Tue, Jun 16, 2009 at 3:40 PM, Thilo Goetz<tw...@gmx.de> wrote:
> I guess I'm just displaying my maven ignorance here.  Since
> we're not uploading any snapshot artifacts to any maven
> repos, does it still buy us anything?

It does. If I build UIMA today, I get a SNAPSHOT version in my local
Maven repository instead of a version that may later interfere with
the final release.

A SNAPSHOT can change from day to day, but a release version should
always stay the same.

BR,

Jukka Zitting

Re: 2.3.0-incubating-SNAPSHOT

[Thilo Goetz <tw...@gmx.de>]

Tommaso Teofili wrote:
> SNAPSHOT is a special version in maven that indicates the latest code;
> typically TRUNK or HEAD in a source control. With this version, maven will
> automatically grab the latest SNAPSHOT every time you build. On the other
> hand, when you are using 2.0, once maven has downloaded this artifact, it
> never tries to get a new 2.0.
> You should use SNAPSHOT for rapidly moving code where bug fixes and
> enhancements are coming fast (our case until the release).
> So I think that -SNAPSHOT shoud remain just before the release for
> developing purposes, and then move to 2.3.0-incuibating.

I guess I'm just displaying my maven ignorance here.  Since
we're not uploading any snapshot artifacts to any maven
repos, does it still buy us anything?

--Thilo

> Just my opinion.
> Regards,
> Tommaso
> 
> 
> 
> 2009/6/16 Thilo Goetz <tw...@gmx.de>
> 
>> Somebody please remind me: what's the purpose of the
>> -SNAPSHOT version name?  Doesn't this just mean that
>> every POM needs to updated twice for a new version,
>> once with the snapshot tag, and once without?
>> Why aren't we going to the next version directly?
>> It's not like we're publishing snapshot releases.
>>
>> --Thilo
>>
> 

Re: 2.3.0-incubating-SNAPSHOT

[Tommaso Teofili <to...@gmail.com>]

SNAPSHOT is a special version in maven that indicates the latest code;
typically TRUNK or HEAD in a source control. With this version, maven will
automatically grab the latest SNAPSHOT every time you build. On the other
hand, when you are using 2.0, once maven has downloaded this artifact, it
never tries to get a new 2.0.
You should use SNAPSHOT for rapidly moving code where bug fixes and
enhancements are coming fast (our case until the release).
So I think that -SNAPSHOT shoud remain just before the release for
developing purposes, and then move to 2.3.0-incuibating.
Just my opinion.
Regards,
Tommaso



2009/6/16 Thilo Goetz <tw...@gmx.de>

> Somebody please remind me: what's the purpose of the
> -SNAPSHOT version name?  Doesn't this just mean that
> every POM needs to updated twice for a new version,
> once with the snapshot tag, and once without?
> Why aren't we going to the next version directly?
> It's not like we're publishing snapshot releases.
>
> --Thilo
>

Re: 2.3.0-incubating-SNAPSHOT

[Thilo Goetz <tw...@gmx.de>]

Michael Baessler wrote:
>>>From my point of view, -SNAPSHOT versions are for example nightly builds.
> For real releases with create a tag in SVN and building on this tag is no SNAPSHOT.

Yes but we don't *do* any nightly builds.  Why do we
go to all this trouble if we don't use it for
anything?

--Thilo

> 
> -- Michael
> 
> Thilo Goetz wrote:
>> Somebody please remind me: what's the purpose of the
>> -SNAPSHOT version name?  Doesn't this just mean that
>> every POM needs to updated twice for a new version,
>> once with the snapshot tag, and once without?
>> Why aren't we going to the next version directly?
>> It's not like we're publishing snapshot releases.
>>
>> --Thilo

Re: 2.3.0-incubating-SNAPSHOT

[Michael Baessler <mb...@michael-baessler.de>]

>From my point of view, -SNAPSHOT versions are for example nightly builds.
For real releases with create a tag in SVN and building on this tag is no SNAPSHOT.

-- Michael

Thilo Goetz wrote:
> Somebody please remind me: what's the purpose of the
> -SNAPSHOT version name?  Doesn't this just mean that
> every POM needs to updated twice for a new version,
> once with the snapshot tag, and once without?
> Why aren't we going to the next version directly?
> It's not like we're publishing snapshot releases.
> 
> --Thilo