| Re: [jsonb-dev] Any idea why "Could not find artifact jakarta.json.bind:jakarta.json.bind-api:jar:3.0.0-SNAPSHOT" failure is occurring? |
We are going try working around the below failure by manually
downloading a
specific snapshot build, that should be enough to help us
generate a TCK signature map for the current 3.0 snapshot spec
jar.
From TCK build-signatures [1] job with maven debug enabled, we are seeing:
"Could not resolve dependencies for project jakarta:dependency_copy:jar:1: Could not find artifact jakarta.json.bind:jakarta.json.bind-api:jar:3.0.0-SNAPSHOT"
The first related debug/warning that we see prior to the above error is:
"
[DEBUG] Could not find metadata jakarta.json.bind:jakarta.json.bind-api:3.0.0-SNAPSHOT/maven-metadata.xml in local (/home/jenkins/.m2/repository)
[DEBUG] Could not find metadata jakarta.json.bind:jakarta.json.bind-api:3.0.0-SNAPSHOT/maven-metadata.xml in local (/home/jenkins/.m2/repository)
[DEBUG] Resolving artifact jakarta.json.bind:jakarta.json.bind-api:pom:3.0.0-SNAPSHOT from [sonatype-nexus-staging (https://jakarta.oss.sonatype.org/content/repositories/staging/, default, releases), eclipse.maven.central.mirror (https://repo.eclipse.org/content/repositories/maven_central/, default, releases)]
[WARNING] The POM for jakarta.json.bind:jakarta.json.bind-api:jar:3.0.0-SNAPSHOT is missing, no dependency information available
"
jakarta.json.bind:jakarta.json.bind-api is the only snapshot artifact that we are trying to access from Eclipse Staging repo, perhaps we need to wait for a more final version to be staged to [2].
For reference, our pom.xml that is trying to access the snapshot is at [3][4].
Any suggestions?
Scott
[1] https://ci.eclipse.org/jakartaee-tck/job/10/job/build-signatures/11/consoleText
[2] https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/json/bind/jakarta.json.bind-api/
[3] https://github.com/eclipse-ee4j/jakartaee-tck/blob/master/docker/pom.xml#L61
[4] https://github.com/eclipse-ee4j/jakartaee-tck/blob/master/docker/pom.xml#L159