When Maven publishes all the sub-components of a single artifact (main jar, sources jar, javadoc jar etc) to Nexus OSSRH, multiple staging repositories are being created.
Some of the sub-components end up in one repository, the others end up in the other one.
Needless to say, each staging repo fails validation, because not all of the required components are present.
This has happened twice in the past hour. I haven't seen it before today so assume something only changed recently.
Publishing from: Travis CI + oraclejdk8 + Maven 3.5.2
Input artifact: org.loadtest4j:loadtest4j:0.19.0
Staging repositories:
Repository | orgloadtest4j-1027 (org.loadtest4j) |
Created | Friday, January 18, 2019 18:19:56 GMT (GMT+0000) |
Updated | Friday, January 18, 2019 18:21:18 GMT (GMT+0000) |
Artifacts | loadtest4j-0.19.0.jar loadtest4j-0.19.0.jar.md5 loadtest4j-0.19.0.jar.sha1 loadtest4j-0.19.0.pom loadtest4j-0.19.0.pom.md5 loadtest4j-0.19.0.pom.sha1 |
Repository | orgloadtest4j-1028 (org.loadtest4j) |
Created | Friday, January 18, 2019 18:20:08 GMT (GMT+0000) |
Updated | Friday, January 18, 2019 18:21:53 GMT (GMT+0000) |
Artifacts | archetype-catalog.xml maven-metadata.xml maven-metadata.xml.md5 maven-metadata.xml.sha1 loadtest4j-0.19.0-javadoc.jar loadtest4j-0.19.0-javadoc.jar.asc loadtest4j-0.19.0-javadoc.jar.md5 loadtest4j-0.19.0-javadoc.jar.sha1 loadtest4j-0.19.0-sources.jar loadtest4j-0.19.0-sources.jar.asc loadtest4j-0.19.0-sources.jar.md5 loadtest4j-0.19.0-sources.jar.sha1 loadtest4j-0.19.0.jar.asc loadtest4j-0.19.0.pom.asc |