-
Notifications
You must be signed in to change notification settings - Fork 2
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
Fix issues #12
Fix issues #12
Conversation
…, if any uncommitted changes are present.
…re snapshot version is not set
…erabilities and add commons-io to dependencies as it is no longer a part of maven-core
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work! Some small things, otherwise mergeable. How should we handle the commits? Squash everything into one big commit that closes the three issues?
src/main/java/com/antonjohansson/versionlifecycleplugin/ValidateMojo.java
Outdated
Show resolved
Hide resolved
src/main/java/com/antonjohansson/versionlifecycleplugin/ValidateMojo.java
Outdated
Show resolved
Hide resolved
Hmm, the |
I stole your commit that fixes the unit tests and put it in this one instead: #13. Lets get that one merged first, so we get the CI build working. |
Remove usage of deprecated methods Apply minor fixes
Remove usage of deprecated methods Fix tests by committing all uncommitted changes before execution Update Java version to 11,update dependencies to avoid high-risk vulnerabilities and add commons-io to dependencies as it is no longer a part of maven-core Allow preparing snapshot for any previous version to avoid a bug, where snapshot version is not set Add a check for uncommitted changes. By default, abort version change, if any uncommitted changes are present. Fix summary output to display correct branch and version Apply minor fixes
I have added the changes to You mentioned that |
Remove usage of deprecated methods Apply minor fixes
Add profile for artifact signing
…apshot for it anymore
Remove usage of deprecated methods Fix tests by committing all uncommitted changes before execution Update Java version to 11,update dependencies to avoid high-risk vulnerabilities and add commons-io to dependencies as it is no longer a part of maven-core Allow preparing snapshot for any previous version to avoid a bug, where snapshot version is not set Add a check for uncommitted changes. By default, abort version change, if any uncommitted changes are present. Fix summary output to display correct branch and version Apply minor fixes
Remove usage of deprecated methods Apply minor fixes
Remove usage of deprecated methods Apply minor fixes
Add profile for artifact signing
Remove usage of deprecated methods Fix tests by committing all uncommitted changes before execution Update Java version to 11,update dependencies to avoid high-risk vulnerabilities and add commons-io to dependencies as it is no longer a part of maven-core Allow preparing snapshot for any previous version to avoid a bug, where snapshot version is not set Add a check for uncommitted changes. By default, abort version change, if any uncommitted changes are present. Fix summary output to display correct branch and version Apply minor fixes
Remove usage of deprecated methods Apply minor fixes
Remove usage of deprecated methods Apply minor fixes
Add profile for artifact signing
Remove usage of deprecated methods Apply minor fixes
Remove usage of deprecated methods Apply minor fixes
The merge-base changed after approval.
Fixes #4
Closes #7
Closes #9
Not entirely sure what's happened there. versions-maven-plugin:set does not seem to assume anything about the branches. It looks like it was trying to update the wrong version (i.e. 0.0.5 -> 0.0.7-SNAPSHOT, when it should have been 0.0.6 -> 0.0.7-SNAPSHOT). It couldn't find it and ignored "set version" altogether. As a result, it didn't work for me on any branch.
Possibly, there was a race condition, and sometimes it worked, sometimes it didn't. I.e. if MavenProject is correctly updated with the correct release version before we attempt to change it to snapshot, then it would work. Or it could have been some changes on Git side?
Anyway, allowing to update any old version seems to do the trick. Tested locally with main and master branches on different projects.
Other