Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.4.0
-
None
-
Moderate
Description
Build will fail behind a maven proxy, like JFrog Artifactory.
The reason is simple: A transitive dependency has a invalid pom.xml (invalid xml):
Example invocation
On any goal:
[ERROR] Failed to execute goal on project cxf-rt-transports-jms: Could not resolve dependencies for project org.apache.cxf:cxf-rt-transports-jms:bundle:3.4.0-SNAPSHOT: Failed to collect dependencies at org.apache.activemq:activemq-pool:jar:5.15.9 -> org.apache.activemq:activemq-jms-pool:jar:5.15.9 -> org.apache.geronimo.specs:geronimo-jta_1.0.1B_spec:jar:1.0.1: Failed to read artifact descriptor for org.apache.geronimo.specs:geronimo-jta_1.0.1B_spec:jar:1.0.1: Could not transfer artifact org.apache.geronimo.specs:specs:pom:1.1 from/to nexus-central (https://mavenproxy.local/maven-central/): Failed to transfer file https://mavenproxy.local/maven-central/org/apache/geronimo/specs/specs/1.1/specs-1.1.pom with status code 409 -> [Help 1] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-remote-resources-plugin:1.6.0:process (default) on project org.apache.cxf.osgi.itests: Execution default of goal org.apache.maven.plugins:maven-remote-resources-plugin:1.6.0:process failed: Failed to resolve dependencies for one or more projects in the reactor. Reason: Unable to get dependency information for org.apache.geronimo.specs:geronimo-jta_1.0.1B_spec:jar:1.0.1: Failed to process POM for org.apache.geronimo.specs:geronimo-jta_1.0.1B_spec:jar:1.0.1: Non-resolvable parent POM for org.apache.geronimo.specs:geronimo-jta_1.0.1B_spec:1.0.1: Could not transfer artifact org.apache.geronimo.specs:specs:pom:1.1 from/to nexus-central (https://mavenproxy.local/maven-central/): Failed to transfer file https://mavenproxy.local/maven-central/org/apache/geronimo/specs/specs/1.1/specs-1.1.pom with status code 409 [ERROR] org.apache.geronimo.specs:geronimo-jta_1.0.1B_spec:jar:1.0.1
Reason / Rationale
If a pom.xml is unreadable, JFrog artifactory will return a HTTP SC 409 instead of just delivering the invalid pom.xml file.
Solution
Either
- Update dependencies (if possible and reasonable). or
- add more excludes – the referenced artifact is already excluded on some other dependencies. or
- do not rely on dependencies with invalid pom.xml files.