On Thu, Jan 21, 2016 at 2:42 PM, Karl Heinz Marbaise <khmarba...@gmx.de> wrote:
> Hi Benson,
>
> you know that you can define the following properties since Maven 3.2.1[1]
>
> ${revision}, ${changelist} and ${sha1} which can be set outside from Maven
> via:
>
> mvn -Drevision=1.2.3-SNAPSHOT ...
>
> and you can use it:
>
> <project..>
> <groupId>...
> <artifactId>...
> <version>${revision}</version>
> ..
> </project>
>
> in case of a multi module build you can also use it in the parent definition
> of the children...
>
>
> but there does not exist some kind of jar which generates the version...as
> far as i know...
that's the disconnect; i thought that JvZ or someone described a
drop-in Jar that could cause a property to come into existence (which
could then be referenced). Of course, I can wrap a script around mvn
if there is no such beast.
>
> Kind regards
> Karl Heinz Marbaise
>
> [1]: http://maven.apache.org/docs/3.2.1/release-notes.html
>
> On 1/20/16 1:11 PM, Benson Margulies wrote:
>>
>> Some time ago, I recall some email about dynamic versioning; the idea
>> being that all the <version/> elements in all the POMs of the project
>> would look like <version>${version}</version>, and a jar dropped into
>> the maven extensions directory would provide a component that would
>> generate the version, perhaps from a git hash or something like that.
>> Is there any doc around on how to set this up? Is it functional in
>> 3.2.5?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
