I want to enforce in every build (not just release builds) that the working copy is pristine (ie doCheck=true for buildnumber plugin), but release:prepare dirties the working copy before running 'clean verify'. 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.
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:[email protected]] Sent: Tuesday, October 24, 2017 4:30 AM To: Maven Users List <[email protected]>; Justin Georgeson <[email protected]> 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 ---------------------------------------------------------------------- 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.
