Hey Richard, I suspect this is related to MDSAL artifact changes, not Nexus infra issues. Adding mdsal-dev list.
Daniel On Mon, Dec 3, 2018 at 6:57 PM Richard Kosegi <[email protected]> wrote: > > Hi infra team, > > I'm currently investigating following failure > https://jenkins.opendaylight.org/releng/job/jsonrpc-maven-verify-neon-mvn35-openjdk8/28/consoleFull#-517142258e5f83968-6a6e-4afa-aebf-7456048eb3ce > > *15:44:07* Caused by: java.io.IOException: Error resolving artifact > org.opendaylight.mdsal:mdsal-common-util:jar:3.0.2: > [Could not find artifact org.opendaylight.mdsal:mdsal-common-util:jar:3.0.2 > in defaultlocal (file:/tmp/r/), > Could not find artifact org.opendaylight.mdsal:mdsal-common-util:jar:3.0.2 in > central (http://repo1.maven.org/maven2/), > Could not find artifact org.opendaylight.mdsal:mdsal-common-util:jar:3.0.2 in > spring.ebr.release > (http://repository.springsource.com/maven/bundles/release/), > Could not find artifact org.opendaylight.mdsal:mdsal-common-util:jar:3.0.2 in > spring.ebr.external > (http://repository.springsource.com/maven/bundles/external/), > Could not transfer artifact > org.opendaylight.mdsal:mdsal-common-util:jar:3.0.2 from/to gemini > (http://zodiac.springsource.com/maven/bundles/release/): > zodiac.springsource.com: Name or service not known] > > Failure comes from SFT, which seems not to be aware of nexus.opendaylight.org. > > We didn't made any changes to pom.xml regarding repositories. > > Any idea what happened? > > Thanks, > > Richard > > _______________________________________________ > infrastructure mailing list > [email protected] > https://lists.opendaylight.org/mailman/listinfo/infrastructure >
_______________________________________________ infrastructure mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/infrastructure
