2009/6/16 Thilo Goetz <twgo...@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:twgo...@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<twgo...@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 >
