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/09/01 16:20:51 UTC
If an extension improves the version, it's not deployed
Using Maven 3.3.9,
https://github.com/basis-technology-corp/auto-version-maven-extension
is not as useful as I had hoped. The extension sets a property for use
in a <version/> element, but 'mvn deploy' deploys the POM as-is, not
after the version is calculated.
Has anyone a suggestion for how to add to this extension to get the
desired behavior?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: If an extension improves the version, it's not deployed
Posted by Benson Margulies <bi...@gmail.com>.
https://github.com/benson-basis/auto-version-example
On Mon, Sep 5, 2016 at 2:09 PM, Karl Heinz Marbaise <kh...@gmx.de> wrote:
> Hi Benson,
>
> On 05/09/16 16:25, Benson Margulies wrote:
>>
>> I just discovered by experiment that that flatten-maven-plugin helps here.
>>
>
> would you so kind to show the setup you have used ?
>
> Might be helpful for others as well...
>
> Thanks for you testing etc.
>
>
> Kind regards
> Karl Heinz
>
>
>>
>> On Thu, Sep 1, 2016 at 1:35 PM, Dan Tran <da...@gmail.com> wrote:
>>>
>>> I wonder if Karl's solution facing the same issue
>>> http://blog.soebes.de/blog/2016/08/08/maven-how-to-create-a-release/
>>>
>>> On Thu, Sep 1, 2016 at 9:20 AM, Benson Margulies <bi...@gmail.com>
>>> wrote:
>>>
>>>> Using Maven 3.3.9,
>>>> https://github.com/basis-technology-corp/auto-version-maven-extension
>>>> is not as useful as I had hoped. The extension sets a property for use
>>>> in a <version/> element, but 'mvn deploy' deploys the POM as-is, not
>>>> after the version is calculated.
>>>>
>>>> Has anyone a suggestion for how to add to this extension to get the
>>>> desired behavior?
>>>>
>
> ---------------------------------------------------------------------
> 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: If an extension improves the version, it's not deployed
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi Benson,
On 05/09/16 16:25, Benson Margulies wrote:
> I just discovered by experiment that that flatten-maven-plugin helps here.
>
would you so kind to show the setup you have used ?
Might be helpful for others as well...
Thanks for you testing etc.
Kind regards
Karl Heinz
>
> On Thu, Sep 1, 2016 at 1:35 PM, Dan Tran <da...@gmail.com> wrote:
>> I wonder if Karl's solution facing the same issue
>> http://blog.soebes.de/blog/2016/08/08/maven-how-to-create-a-release/
>>
>> On Thu, Sep 1, 2016 at 9:20 AM, Benson Margulies <bi...@gmail.com>
>> wrote:
>>
>>> Using Maven 3.3.9,
>>> https://github.com/basis-technology-corp/auto-version-maven-extension
>>> is not as useful as I had hoped. The extension sets a property for use
>>> in a <version/> element, but 'mvn deploy' deploys the POM as-is, not
>>> after the version is calculated.
>>>
>>> Has anyone a suggestion for how to add to this extension to get the
>>> desired behavior?
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: If an extension improves the version, it's not deployed
Posted by Benson Margulies <bi...@gmail.com>.
I just discovered by experiment that that flatten-maven-plugin helps here.
On Thu, Sep 1, 2016 at 1:35 PM, Dan Tran <da...@gmail.com> wrote:
> I wonder if Karl's solution facing the same issue
> http://blog.soebes.de/blog/2016/08/08/maven-how-to-create-a-release/
>
> On Thu, Sep 1, 2016 at 9:20 AM, Benson Margulies <bi...@gmail.com>
> wrote:
>
>> Using Maven 3.3.9,
>> https://github.com/basis-technology-corp/auto-version-maven-extension
>> is not as useful as I had hoped. The extension sets a property for use
>> in a <version/> element, but 'mvn deploy' deploys the POM as-is, not
>> after the version is calculated.
>>
>> Has anyone a suggestion for how to add to this extension to get the
>> desired behavior?
>>
>> ---------------------------------------------------------------------
>> 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: If an extension improves the version, it's not deployed
Posted by Dan Tran <da...@gmail.com>.
I wonder if Karl's solution facing the same issue
http://blog.soebes.de/blog/2016/08/08/maven-how-to-create-a-release/
On Thu, Sep 1, 2016 at 9:20 AM, Benson Margulies <bi...@gmail.com>
wrote:
> Using Maven 3.3.9,
> https://github.com/basis-technology-corp/auto-version-maven-extension
> is not as useful as I had hoped. The extension sets a property for use
> in a <version/> element, but 'mvn deploy' deploys the POM as-is, not
> after the version is calculated.
>
> Has anyone a suggestion for how to add to this extension to get the
> desired behavior?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>