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:
Dependency resolution then fails with: It seems that, because it is using Ivy under the covers, Gradle is falling victim to https://issues.apache.org/jira/browse/IVY-899 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)? -- View this message in context: http://gradle.1045684.n5.nabble.com/Dependencies-of-type-eclipse-plugin-tp5448574p5448574.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
