Major If a maven-metadata.xml file merge fails in Nexus 3 the repository ID with bad metadata is not logged, even at ROOT DEBUG. This makes it extremely difficult to find where the problematic file is.
2017-05-12 16:41:57,460+0000 WARN [qtp359682993-47] test org.sonatype.nexus.repository.httpbridge.internal.ViewServlet - Failure servicing: GET /repository/public/org/apache/maven/wagon/wagon-ssh/maven-metadata.xml java.io.EOFException: input contained no data at org.codehaus.plexus.util.xml.pull.MXParser.fillBuf(MXParser.java:3037) [na:na] at org.codehaus.plexus.util.xml.pull.MXParser.more(MXParser.java:3080) [na:na] at org.codehaus.plexus.util.xml.pull.MXParser.parseProlog(MXParser.java:1451) [na:na] at org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1436) [na:na] at org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1131) [na:na] at org.apache.maven.artifact.repository.metadata.io.xpp3.MetadataXpp3Reader.read(MetadataXpp3Reader.java:913) [na:na] at org.apache.maven.artifact.repository.metadata.io.xpp3.MetadataXpp3Reader.read(MetadataXpp3Reader.java:519) [na:na] at org.apache.maven.artifact.repository.metadata.io.xpp3.MetadataXpp3Reader.read(MetadataXpp3Reader.java:548) [na:na] at org.sonatype.nexus.repository.maven.internal.MavenModels.readMetadata(MavenModels.java:83) [na:na] at org.sonatype.nexus.repository.maven.internal.group.RepositoryMetadataMerger.merge(RepositoryMetadataMerger.java:73) [na:na] at org.sonatype.nexus.repository.maven.internal.group.MavenGroupFacet.mergeAndCache(MavenGroupFacet.java:125) [na:na] at org.sonatype.nexus.repository.maven.internal.group.MergingGroupHandler.doGet(MergingGroupHandler.java:98) [na:na] at org.sonatype.nexus.repository.group.GroupHandler.handle(GroupHandler.java:79) [na:na] at org.sonatype.nexus.repository.view.Context.proceed(Context.java:80) [na:na]