Skip to content
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

Closed
vlsi opened this issue Feb 24, 2016 · 5 comments
Closed

Update version in pom.xml #67

vlsi opened this issue Feb 24, 2016 · 5 comments

Comments

@vlsi
Copy link
Contributor

vlsi commented Feb 24, 2016

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.

@sameb
Copy link
Contributor

sameb commented Feb 24, 2016

The 3.2.1 release should have the correct pom, see
http://central.maven.org/maven2/cglib/cglib/3.2.1/cglib-3.2.1.pom . I just
need to run the release plugin again on the main branch to up the version
to a snapshot.

On Wed, Feb 24, 2016 at 4:29 PM Vladimir Sitnikov notifications@github.com
wrote:

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.


Reply to this email directly or view it on GitHub
#67.

@vlsi
Copy link
Contributor Author

vlsi commented Feb 25, 2016

I just need to run the release plugin again on the main branch

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.

@sameb
Copy link
Contributor

sameb commented Feb 25, 2016

AFAIK, master should really be vNext-SNAPSHOT, anyway, not the last
released version. So I'd need to run it again to set it to the correct next
snapshot version.

On Wed, Feb 24, 2016, 8:30 PM Vladimir Sitnikov notifications@github.com
wrote:

I just need to run the release plugin again on the main branch

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.


Reply to this email directly or view it on GitHub
#67 (comment).

@vlsi
Copy link
Contributor Author

vlsi commented Feb 25, 2016

master should really be vNext-SNAPSHOT

sure.

I typically see [maven-release-plugin] prepare release .., [maven-release-plugin] prepare for next development iteration pair of release-plugin-induced-commits (see here: https://github.com/pgjdbc/pgjdbc/commits/master)

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.

@sameb
Copy link
Contributor

sameb commented Apr 9, 2016

done,

@sameb sameb closed this as completed Apr 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants