Maven Config Missing Jar Files With SNAPSHOT
(Doc ID 2306661.1)
Last updated on JUNE 19, 2019
Applies to:Oracle JDeveloper - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 12c]
Information in this document applies to any platform.
On : 22.214.171.124.0 version, JDeveloper Installation (Download, Install, Extensions, etc.)
The maven-sync job still fails and stops, when it tries to populate SNAPSHOT versions to a non-Snapshot repository.
Repository copy will not be performed for this artifact:
org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to deploy metadata:
Could not transfer metadata com.oracle.jdev:tyrus-client-1.3-SNAPSHOT/maven-metadata.xml from/to
Failed to transfer file: https://FOO/nexus/content/repositories/oracle-soa-tools/com/oracle/jdev/tyrus-client-1.3-SNAPSHOT/maven-metadata.xml.
Return code is: 400, ReasonPhrase: Bad Request.
Removing any SNAPSHOT version jar file from the upload maven plugin lists makes the maven-sync complete successfully
Can happen with a Nexus repository.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document