Hi,
On 24/10/17 15:59, Justin Georgeson wrote:
I want to enforce in every build (not just release builds)
> that the working copy is pristine
>
(ie doCheck=true for buildnumber plugin),
On a CI server or locally ?
but release:prepare dirties the working copy before running 'clean verify'.
Of course it does cause it changes the pom files to represent the
correct version...and commit this state of the change back to version
control...
So when I run release:prepare the buildnumber plugin fails. I can work around
it by running 'mvn release:prepare
> -Darguments="-Dmaven.buildNumber.doCheck=false"' but that just seems
hacky, so I was curious if there's a better way.
You know about the release:prepare goal what it is exactly doing ?
http://maven.apache.org/maven-release/maven-release-plugin/examples/prepare-release.html
Maybe I misunderstand your question but it sounds like you are trying to
resolve a thing which has been solved by maven-release-plugin already?...
Kind regards
Karl Heinz Marbaise
Looks like if I configure a default property value for
maven.buildNumber.doCheck to true, then I can have a profile activate when file
release.properties exists to set the doCheck property to false, and that gets
me through release:prepare. Any pitfalls I might be walking into with something
like that?
-----Original Message-----
From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de]
Sent: Tuesday, October 24, 2017 4:30 AM
To: Maven Users List <users@maven.apache.org>; Justin Georgeson
<justin.george...@halliburton.com>
Subject: [EXTERNAL] Re: how to use both buildnumber-maven-plugin and
maven-release-plugin
External Sender: Use caution with links/attachments.
Hi,
the question is what the real problem is?
Can you have an example project which shows the problem? Or can you describe
more in detail what exactly does not work or not work like you expect it..
Kind regards
Karl Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
