[GRADLE-2076] Artifact not found resolving dependencies with packaging/type "eclipse-plugin" Created: 01/Feb/12 Updated: 04/Jan/13 Resolved: 10/Feb/12
|Reporter:||Gradle Forums||Assignee:||Daz DeBoer|
I'm currently writing a JaCoCo gradle plugin and have a dependency on the JaCoCo modules. Unfortunately, the pom for the modules specifies that the jar files have packaging "eclipse-plugin". This appears to translate into a resolved dependency which, when printed, looks like:
[[ResolvedArtifact dependency:org.jacoco:org.jacoco.agent:0.5.6.201201232323;default name:org.jacoco.agent classifier:null extension:eclipse-plugin type:eclipse-plugin]
Dependency resolution then fails with:
Could not resolve all dependencies for configuration ':services:agent:testRuntime'.
It seems that, because it is using Ivy under the covers, Gradle is falling victim to IVY-899 .
An example pom from one of the JaCoCo modules:
<project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
Is there a workaround available in Gradle (SBT has one for example)?
|Comment by Gradle Forums [ 01/Feb/12 ]|
Your analysis is essentially correct: thanks for pointing out IVY-899. However due to changes required to the pom parsing code, we've already forked the ivy code involved, so we shouldn't need to wait for an ivy fix (we can do it ourselves).
Currently, Gradle has special handling for "pom", "ejb", "bundle" and "maven-plugin"; otherwise we just map the "packaging" value to the extension of the main artifact. Do you have any documentation on what are the allowable packaging values in maven, and how they should be mapped? I can't find anything comprehensive.
A possible workaround would be to use a "Client Module" to declare this dependency: http://gradle.org/docs/current/usergu.... Gradle would then override the published metadata with the dependency metadata declared in your build script. This can be done on a per-dependency basis.
|Comment by Daz DeBoer [ 10/Feb/12 ]|
Maven pom modules with packing = 'eclipse-plugin' are now assumed to have 'jar' artifacts.
|Comment by Ryan J [ 13/Mar/12 ]|
This is also a problem for Jetty. One of the artifacts uses orbit packaging with a jar extension.
I think this is a mailing list post explaining what they're trying to accomplish, but it's long and I can't find a decent threaded version of the conversation.
This works for me (for now).
There's also jbi-component and jbi-shared-library suggested in IVY-899.
I might be wrong, but Maven seems to default to jar if <type></type> isn't specified in the dependency declaration. Would defaulting to jar for unknown packaging types cause problems with Gradle (or Ivy for that matter)?