maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Hüttermann <mich...@huettermann.net>
Subject Re: Lightweight maven-releases, or an alternative to the maven-release-plugin
Date Thu, 02 May 2013 16:27:29 GMT
Hello,
if interested: the topic of lightweight maven releases is discussed in
"DevOps for Developers", Apress, Chapter 8.



Cheers,
Michael




> Hello there,
>
> I. find prepare and perform quite heavyweight my self. After prepare did
> build everything successfully, it throws away everything, just tags the
> source and starts over again during perform.
>
> prepare already checks with scm means, that there are no modifications and
> in my experience tagging is the most harmless operation in the whole
> process (well, would I still use CVS that could be different).
>
> So running prepare with prepareGoals set to "-DperformRelease=true clean
> deploy" does what *I* want.
>
> - checks I have everything in SCM
> - does modify POMs for release.
> - deploys to staging
> - only on success of this tags the sources
> - go back to SNAPSHOT.
>
> git and svn (when not doing the strange remoteTagging) are capable of
> tagging always.
> Worst thing that might happen: bad stuff in staging for a short time.
>
> Regards Mirko
> --
> Sent from my mobile
> On May 1, 2013 9:15 PM, "Robert Scholte" <rfscholte@apache.org> wrote:
>
>> Graham, well said.
>>
>> Although the pom.xml is the easiest way to discover the version, it is
>> not
>> the best location, since it would require a commit.
>> The solution must be found in a generated file which will be added to
>> the
>> artifact during packaging. Here you could add a timestamp or revision.
>>
>> Robert
>>
>> Op Wed, 01 May 2013 12:44:19 +0200 schreef Graham Leggett <
>> minfrin@sharp.fm>:
>>
>>  On 30 Apr 2013, at 11:21 PM, Roger Brechbühl <rotscher.ch@gmail.com>
>>> wrote:
>>>
>>>  Maybe somebody is interested in how a release could be built in a more
>>>> lightweight and safe way than with the maven-release-plugin.
>>>> Especially
>>>> recommended for nightly releases.
>>>>
>>>> It's not yet released, but basically fully working:
>>>>
>>>> *mvn clean install -Dversion.override=1.2.3-S-5*
>>>>
>>>> https://github.com/rotscher/**emerging/tree/version.**
>>>> override-with_maven_install-2.**4<https://github.com/rotscher/emerging/tree/version.override-with_maven_install-2.4>
>>>>
>>>
>>> Maven has a very clear definition of a "release", being an artefact
>>> that
>>> can traced back to the precise code via a tag, and a build that can be
>>> repeated. This is as opposed to a snapshot, which has no well defined
>>> origin.
>>>
>>> You might approach this two ways, you might create "nightly snapshots"
>>> and have them deployed somewhere suitable, using "mvn deploy".
>>>
>>> Alternatively if you want to create proper "nightly releases" (in the
>>> maven sense), you could feed a custom version number into the release
>>> plugin to represent your release, but this starts to smell like "that's
>>> what a snapshot is for".
>>>
>>> Regards,
>>> Graham
>>> --
>>>
>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail:
>> users-unsubscribe@maven.**apache.org<users-unsubscribe@maven.apache.org>
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Mime
View raw message