versions:lock-snapshots and then
versions:unlock-snapshots to turn them back to normal before reintegrating your branch 2009/4/22 Michael Hüttermann <[email protected]> > ok, I see, thanks! There is another concept using a generic version: > snapshots. What do you do with your SNAPSHOTs while branching then? Do you > go through all your POMs and dependencies replacing the snapshot token > with the real snapshot version including timestamp? You can say "ok, I > will never use RELEASE" but you want to use the snapshot mechanism in the > daily work for sure I guess. What's your strategy here while branching ? > > Thanks for your time !!! > > Michael > > > > > 2009/4/22 Michael Hüttermann <[email protected]> > > > >> Hello experts, > >> > >> how do you set up the process if you use RELEASE for a dependency in a > >> POM, and work with VCS branches ? > > > > > > you stop using RELEASE for a dependency. > > > > RELEASE corresponds to the last released version... so if you release, in > > order > > > > 1.0.0 > > 1.0.1 > > 1.1.0 > > 1.1.1 > > 2.0.0 > > 1.0.2 > > > > Then RELEASE will correspond to 1.0.2 as that was the last version > > released. > > > > The solution is to use version ranges, i.e. work on the 1.0.x branch > would > > depend on [1.0.0,1.1.0-!) that is any version greater than or equal to > > 1.0.0 > > and less than 1.1.0-! (which thanks to the joys of ascii sorting means > > that > > you will exclude any 1.1.0 version including 1.1.0-SNAPSHOT which is less > > than 1.1.0) > > > > Of course version ranges only work if you follow maven's rules for > version > > numbering... if you cannot follow maven's (some would say slightly > > strange) > > version numbering scheme you will need to do some manual work... to help > > automate the manual work, you'll probably end up using > > versions-maven-plugin > > and specifying the version using a property. > > > > > >> What is your best practice? Probably a > >> branch will have to adress another, older version of an artifact, > >> actually > >> it has to adress a stable, tagged version. What happens if on HEAD you > >> use > >> new versions of dependencies (so a new version for RELEASE), ... do you > >> adjust all of your branches to remove the RELEASE token and enter a > >> dedicated version? Isn't that a nightmare ? > > > > > > I think you will realise from my earlier comment that there is *no way in > > hell* that you would use RELEASE. > > > > FYI, the LATEST and RELEASE versions were initially more for use in > > specifying plugin versions... but they are so problematic that everyone > > pretty much avoids them > > > > -Stephen > > > >> > >> > >> Thanks !! > >> > >> > >> Michael > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
