You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Benson Margulies <bi...@gmail.com> on 2016/01/20 13:11:47 UTC
CD versioning
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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: CD versioning
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi Jason,
sounds interessting.. ;-)..
Kind regards
Karl Heinz
On 1/22/16 3:17 AM, Jason van Zyl wrote:
> I have something that I wouldn’t make public but you’re free to hack it up and do what you like with it.
>
>> On Jan 21, 2016, at 11:47 AM, Benson Margulies <bi...@gmail.com> wrote:
>>
>> On Thu, Jan 21, 2016 at 2:42 PM, Karl Heinz Marbaise <kh...@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-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
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Takari and Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> ---------------------------------------------------------
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: CD versioning
Posted by Jason van Zyl <ja...@takari.io>.
You need to catch me on IRC. I check my email once or twice a day.
> On Jan 27, 2016, at 9:17 AM, Benson Margulies <bi...@gmail.com> wrote:
>
> Jason, ping?
>
>
> On Mon, Jan 25, 2016 at 7:36 AM, Benson Margulies <bi...@gmail.com> wrote:
>> I'm in. How non-public do you need it to be? On github quietly, or
>> passed along through some other channel? Either way is fine with me.
>>
>>
>> On Thu, Jan 21, 2016 at 9:17 PM, Jason van Zyl <ja...@takari.io> wrote:
>>> I have something that I wouldn’t make public but you’re free to hack it up and do what you like with it.
>>>
>>>> On Jan 21, 2016, at 11:47 AM, Benson Margulies <bi...@gmail.com> wrote:
>>>>
>>>> On Thu, Jan 21, 2016 at 2:42 PM, Karl Heinz Marbaise <kh...@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-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
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> Founder, Takari and Apache Maven
>>> http://twitter.com/jvanzyl
>>> http://twitter.com/takari_io
>>> ---------------------------------------------------------
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: 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
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: CD versioning
Posted by Benson Margulies <bi...@gmail.com>.
Jason, ping?
On Mon, Jan 25, 2016 at 7:36 AM, Benson Margulies <bi...@gmail.com> wrote:
> I'm in. How non-public do you need it to be? On github quietly, or
> passed along through some other channel? Either way is fine with me.
>
>
> On Thu, Jan 21, 2016 at 9:17 PM, Jason van Zyl <ja...@takari.io> wrote:
>> I have something that I wouldn’t make public but you’re free to hack it up and do what you like with it.
>>
>>> On Jan 21, 2016, at 11:47 AM, Benson Margulies <bi...@gmail.com> wrote:
>>>
>>> On Thu, Jan 21, 2016 at 2:42 PM, Karl Heinz Marbaise <kh...@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-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
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Takari and Apache Maven
>> http://twitter.com/jvanzyl
>> http://twitter.com/takari_io
>> ---------------------------------------------------------
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: 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
Re: CD versioning
Posted by Benson Margulies <bi...@gmail.com>.
I'm in. How non-public do you need it to be? On github quietly, or
passed along through some other channel? Either way is fine with me.
On Thu, Jan 21, 2016 at 9:17 PM, Jason van Zyl <ja...@takari.io> wrote:
> I have something that I wouldn’t make public but you’re free to hack it up and do what you like with it.
>
>> On Jan 21, 2016, at 11:47 AM, Benson Margulies <bi...@gmail.com> wrote:
>>
>> On Thu, Jan 21, 2016 at 2:42 PM, Karl Heinz Marbaise <kh...@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-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
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Takari and Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> ---------------------------------------------------------
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: 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
Re: CD versioning
Posted by Jason van Zyl <ja...@takari.io>.
I have something that I wouldn’t make public but you’re free to hack it up and do what you like with it.
> On Jan 21, 2016, at 11:47 AM, Benson Margulies <bi...@gmail.com> wrote:
>
> On Thu, Jan 21, 2016 at 2:42 PM, Karl Heinz Marbaise <kh...@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-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
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: CD versioning
Posted by Benson Margulies <bi...@gmail.com>.
On Thu, Jan 21, 2016 at 2:42 PM, Karl Heinz Marbaise <kh...@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-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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: CD versioning
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
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...
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-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