Details
-
Type:
Improvement
-
Status:
Resolved
-
Resolution: Fixed
-
Affects Version/s: 0.8
-
Fix Version/s: 1.0-milestone-9
-
Gradle Forums topic Reference:
Description
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'.
Cause: Artifact 'org.jacoco:org.jacoco.agent:0.5.6.201201232323@eclipse-plugin' not found
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">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.jacoco</groupId>
<artifactId>org.jacoco.build</artifactId>
<version>0.5.6.201201232323</version>
<relativePath>../org.jacoco.build</relativePath>
</parent>
<artifactId>org.jacoco.report</artifactId>
<packaging>eclipse-plugin</packaging>
<name>JaCoCo :: Report</name>
<description>JaCoCo Reporting</description>
<dependencies>
<dependency>
<groupId>${project.groupId}</groupId>
<artifactId>org.jacoco.core</artifactId>
</dependency>
</dependencies>
<build>
<sourceDirectory>src</sourceDirectory>
</build>
</project>
Is there a workaround available in Gradle (SBT has one for example)?