-
Notifications
You must be signed in to change notification settings - Fork 886
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
Update version in pom.xml #67
Comments
The 3.2.1 release should have the correct pom, see On Wed, Feb 24, 2016 at 4:29 PM Vladimir Sitnikov notifications@github.com
|
Why running again? Can you probably just "reset master to the relevant commit"? Anyway, it is just strange that master branch is behind, thus the issue. |
AFAIK, master should really be vNext-SNAPSHOT, anyway, not the last On Wed, Feb 24, 2016, 8:30 PM Vladimir Sitnikov notifications@github.com
|
sure. I typically see Anyway would work for me here. It was just strange that current master points to 3.2.0-SNAPSHOT while 3.2.1 was in Central. |
done, |
3.2.1 is released, yet pom.xml reads 3.2.0.
maven-release-plugin should probably be configured to keep versions consistent.
JFYI: I've went though configuration of maven-release-publish-to-central projects recently, however it requires oss.sonatype grants to test the procedure.
The text was updated successfully, but these errors were encountered: