[gradle-user] pom generation and inherited dependencies

[Levi Hoogenberg]

Hi,

I'm trying to use Gradle to generate pom files, so that I can create an
online M2 repository that contains my project's artifacts. Eventually, I'd
like to use Sonatype for this, but this way seemed less time-consuming.

Anyway, my project declares two custom configurations:

    configurations {
        distribution
        apiDocs.extendsFrom distribution
        compile.extendsFrom apiDocs
    }

(All JAR files in the distribution configuration will be packaged in the
distribution zip, the apiDocs JARs form the classpath for the Javadoc task.)

Now, when I run *gradle install*, the modules' generated pom.xmls do contain
a <dependency> element for each dependency in the compile configuration, but
none for the distribution or apiDocs configurations' dependencies.

Is this intended behaviour? Can I use some workaround to get the behaviour I
would like?

Thanks,
  Levi