Gradle isn't particularly au-fait with the maven packaging element. We have special handling for "pom" and "jar"; otherwise we just map the "packaging" value to the extension of the main artifact. I assume this is wrong in the case of the 'eclipse-plugin' packaging!
Do you have any documentation on how this packaging should be properly handled? One solution for now might be to use a "Client Module" to declare this dependency: http://gradle.org/docs/current/userguide/dependency_management.html#sub:client_module_dependencies cheers Daz On 29 January 2012 13:55, Andres Almiray <aalmi...@yahoo.com> wrote: > Case in point: the jacoco dependencies are packages as eclipse-plugin. See > > > https://repository.sonatype.org/service/local/repositories/central-proxy/content/org/jacoco/org.jacoco.core/0.5.3.201107060350/org.jacoco.core-0.5.3.201107060350.pom > > <artifactId>org.jacoco.core</artifactId> > <packaging>eclipse-plugin</packaging> > <name>JaCoCo :: Core</name> > <description>JaCoCo Core</description> > > The JAR is available from mavenCentral but gradle/wharf refuses to > download it. I can only see the pom file inside > ~/.gradle/caches/artifacts-4/org.jacoco/org.jacoco.core/* > > There must be a better way to fix this than downloading all jars and > setting up a flatDir repository :-( > -- Darrell (Daz) DeBoer Principal Engineer, Gradleware http://www.gradleware.com
