New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When using revapi.singleVersionForAllModules, a version tag is added to each child POM. #135
Comments
I imagine it could work the same as
Thanks! |
Hi metlos, thanks for the quick reponse! You are right, it should be the same behavior as versions:set in my view :) I will respond to the scenarios in order. The command I run in each case: mvn package revapi:update-versions -Drevapi.singleVersionForAllModules=true -Djavax.xml.accessExternalSchema=all
In general, I believe that if not running from root while specifying revapi.singleVersionForAllModules=true, the response should be an error advising me or the ... error of my ways :D |
This is now fixed in |
Hi,
As per the title: When using revapi.singleVersionForAllModules, a version tag is added to each child POM.
This is not desirable when using update-versions or update-release properties when the version is inherited from the parent POM. Would it be possible to change how this works, or add an option to turn this behavior on/off?
The text was updated successfully, but these errors were encountered: