Right, the updateReleaseInfo param will IIRC just add the release being
deployed to the list. Not rebuild old data. That's why you need Sonatype to
fix old data and then the updateReleaseInfo param needs to be used for
future releases (which should be the case if the release-profile profile
from th
thank you Anders: I think I'll create a MVNCENTRAL issue and report here to
share experience on this common scenario
On the updateReleaseInfo parameter of deploy plugin, I don't see how this can
rebuild the versions list from the real content in the repository
Regards,
Hervé
Le mardi 6 mars 2
This is very often an issue. I know for sure that Nexus can fix this so you
could ask Sonatype via Jira. That would rebuild old data.
For future releases I believe this is the correct way of fixing this in
m-deploy-p:
http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#updateRelea
Hi,
In Jansi, there is an issue with the list of artifacts versions: some old
artifacts published on Central are not listed in the metadata (I don't know
why/when they disappeared).
Here is the maven-metadata.xml [1] which lists versions 1.12 to 1.17
But the directory contains also versions 1.2.
