ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin" <xavier.ha...@gmail.com>
Subject Re: Problem with transitive dependencies
Date Mon, 25 Jun 2007 16:01:25 GMT
On 6/22/07, Oystein Aadland <ivy_listuser@lookoutpoint.org> wrote:
>
>
> Well. I've been browsing the source code and it looks like this works if I
> put explicit includes for the missing Module C artifacts in Module A.
>
> I thought that putting a dependency for a spesific configuration by
> default
> means all artifacts for that dependency. It certainly works that way if
> there's no other "conflicting" modules in the dependency list.
>
> This smells like a bug to me. In the code (IvyNode.loadData) a dependency
> is
> only loaded if it hasn't been loaded before (first if). At the end of this
> method explisit includes are added. If my assumption about what should
> default be included is right then all artifacts for the given
> configuration
> should have been added if the include list is empty.
>
> Anyone out there that nows if my reasoning is correct?


Indeed, your reasonning seems correct. Since A depends on C with no artifact
restriction you should get all C artifacts when resolving A dependencies.
Could you please open an issue in JIRA?

Xavier

Oystein
> --
> View this message in context:
> http://www.nabble.com/Problem-with-transitive-dependencies-tf3957355.html#a11248224
> Sent from the ivy-user mailing list archive at Nabble.com.
>
>


-- 
Xavier Hanin - Independent Java Consultant
Manage your dependencies with Ivy!
http://incubator.apache.org/ivy/

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