ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mitch Gitman <>
Subject Re: install task from Maven repo misses TRANSITIVE source artifacts
Date Wed, 02 Dec 2009 19:21:22 GMT
Apologies for the noise. Apparently, I didn't search this matter thoroughly
enough before I posted. I realize now it's already a well-known issue.

Here's the relevant JIRA issue:

And the relevant ivy-user discussion thread:

On Wed, Dec 2, 2009 at 10:48 AM, Mitch Gitman <> wrote:

> Well, this is one of those moments when I just want to slap myself on the
> forehead. It should have been obvious why Ivy wasn't getting source and
> Javadoc for transitive dependencies. Because source and Javadoc get their
> own Ivy confs in the generated ivy.xml, and those corresponding confs
> weren't being specified on the dependencies.
> Here's just one dependency from the ivy.xml that gets generated for the
> root pom.xml:
> <dependency org="org.apache.commons" name="commons-cli" rev="1.2"
>             force="true"
>             conf="compile->compile(*),master(*);runtime->runtime(*)">
> To get the source and Javadoc, the conf attribute's value really should be
> something like:
> "compile->compile(*),master(*);runtime->runtime(*);sources->sources;javadoc->javadoc
> "
> So really, the more precise question is, for the ivy.xml that Ivy generates
> from a POM, why isn't it applying the "sources" and "javadoc" confs to the
> dependencies? Was there a decision involved? Is this something that could be
> made configurable?
> This may go back to some of the technical issues with Maven integration
> raised in the "sources as conf or type" thread on this list, some of which I
> didn't fully grasp at the time.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message