Nexus error updating group repository metadata

In our case, we have a third-party continuous deployment product which expects valid Maven metadata in order to resolve the snapshot artifacts and then deploy them to the respective environments.

Teams are resorting to the really unorthodox approach of building their code with Gradle and then deploying it with Maven using the goal, just so that they would have properly generated Maven Metadata.

Gradle will continue to issue HEAD requests to determine the existence of classified artifacts, and will ignore the element.

I really don't understand the purpose of listing each snapshot artifact, since the same indexing information isn't published anywhere for non-SNAPSHOT artifacts, AFAIK.

You mentioned this can break things, could you give me an example? I would like to point out that Maven 2.x has been EOL-ed in November 2009.

This legacy mode was intended for the expected timeframe during which people would be migrating off Maven 2.x to 3.x.

In a way I might agree that this is only for snapshots, but...

If this is how it works in the Maven world and you are using and producing Maven dependencies (after all), this is what you need to follow. If you would like to discuss this further, I would recommend contacting the Maven Developers distribution list.

This is produced by artifact repository managers and is used by IDE-s and other artifact repository managers.

The fact that Maven repositories across the various repository managers are called "Maven 2" is irrelevant.

As Maven 2.x has been EOL-ed, it would only make sense to support the current format.

I like the idea of making this change in the next major version of Gradle, so that we can document this as a potentially breaking change.

We are already planning some other breaking changes related to Maven compatibility (e.g handle @carlspring Is creating the full history necessary for your tool or was it just failing because of the old format?

Leave a Reply