cstamas commented on issue #11596: URL: https://github.com/apache/maven/issues/11596#issuecomment-3681410727
Howdy, as you say, _without_ MRM prefix resolution works as expected, thus, it has to be your MRM that has some invalid metadata. Based on your mirror config I assume you use NX w/ public "supergroup". Try out these (replace URL to your): ``` $ curl http://our.internal.nexus.host.se/content/groups/public/com/diffplug/spotless/maven-metadata.xml $ curl http://our.internal.nexus.host.se/content/groups/public/org/apache/avro/maven-metadata.xml ``` The corresponding metadata in Maven Central are these: * https://repo.maven.apache.org/maven2/com/diffplug/spotless/maven-metadata.xml -- spotless _has no_ G level Maven Metadata * https://repo.maven.apache.org/maven2/org/apache/avro/maven-metadata.xml -- avro has G level Maven Metadata Try to figure out from where the corrupt metadata comes from, that Makes maven wrongly resolve the group. Also, try to use `-X` (use less or something similar as you will get a LOT of log), and try to figure out what Maven does: ``` [DEBUG] Resolving plugin prefix spotless from [eu.maveniverse.maven.plugins, org.apache.maven.plugins, org.codehaus.mojo] ... [DEBUG] Resolved plugin prefix spotless to com.diffplug.spotless:spotless-maven-plugin from repository null ``` Finally, re-supergroups, my own stance: https://maveniverse.eu/blog/2025/11/09/why-are-mrm-group-repositories-bad/ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
