Maven Release Plugin - indicated version not on Maven Central

[martinjoconnor]

I have a set of projects that I deploy on Maven Central. I use the Maven Release plugin to perform this deployment.

The latest Maven Release Plugin version on Maven Central is 2.5.3.

The VersionEye-indicated latest version is 3.0-r1585899.

I cannot use the 3.0-r1585899 version in my project because the Maven Central deploy fails because it cannot find this dependency. Which means a permanent 'dependency out of date' VersionEye status.

It would be nice if there was some way to configure VersionEye to indicate that only a particular repository (e.g., Maven Central) should be considered as the source of the latest version of dependencies?

(And should 3.0-r1585899 really be treated at the latest stable release?)

TIA

[Robert Reiz]

@martinjoconnor Can you post the exact group and artefact ID please? I would need that to take a look to your case.

I remember that I removed a 3.0-rX version a couple days ago, but not sure if we are talking about the same artefact!

[Robert Reiz]

@martinjoconnor Are you using this artefact: https://www.versioneye.com/java/org.apache.maven.plugins:maven-release-plugin/2.5.3 ?

[martinjoconnor]

Yes - 2.5.3. Looks like this is fixed now. Thanks!

[Robert Reiz]

Done!