Hi Pascal,
Unfortunately this method results in pom files being deployed with releases
that do not have corresponding versions in them.
In fact, the version is literally:
<version>${revision}</version>
This results in build warnings for consumers of the released artifact.
Cheers,
Steve C
> On 24 Oct 2017, at 8:27 pm, Pascal <pascal.gr...@gmail.com> wrote:
>
> For me it's hard to understand the problem you are having, it might help to
> specify the exact errors you are getting.
>
> If you are willing to try something other than the release plugin, have a
> look at https://axelfontaine.com/blog/dead-burried.html
>
> Cheers,
>
> Pascal
>
>
> 2017-10-23 18:40 GMT+02:00 Justin Georgeson <
> justin.george...@halliburton.com>:
>
>> The 'clean verify' invoked by release:prepare fails in
>> buildnumber-maven-plugin because pom.xml is modified. I can pass arguments
>> to release:prepare have buildnumber-maven-plugin skip the check for
>> modifications, but that check is one of the main motivations for using it
>> in the first place. What are other people doing here?
>>
>> ----------------------------------------------------------------------
>> This e-mail, including any attached files, may contain confidential and
>> privileged information for the sole use of the intended recipient. Any
>> review, use, distribution, or disclosure by others is strictly prohibited.
>> If you are not the intended recipient (or authorized to receive information
>> for the intended recipient), please contact the sender by reply e-mail and
>> delete all copies of this message.
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
