maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte" <rfscho...@apache.org>
Subject Re: Lightweight maven-releases, or an alternative to the maven-release-plugin
Date Wed, 01 May 2013 19:15:38 GMT
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
>
> 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
For additional commands, e-mail: users-help@maven.apache.org


Mime
View raw message