Hi,
On 25/10/17 08:50, Stephen Coy wrote:
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.
If you like to use a property for the version. First you have to use
Maven 3.5.0+ and furthermore flatten-maven-plugin as described in the
docs about that[1].
Kind regards
Karl Heinz Marbaise
[1]: http://maven.apache.org/maven-ci-friendly.html
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?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
