ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée (JIRA) <>
Subject [jira] Commented: (IVY-810) Duplidate entries after a resolve.
Date Sat, 26 Apr 2008 09:08:55 GMT


Nicolas Lalevée commented on IVY-810:

The warning you get is about a module which you are trying to get in two different configurations.
Ivy does the resolve and evict conflits for only one configuration at a time. The resolve
process is one by one configuration. If you have a use case where you have to build a classpath
with a lot of different configuration, then you should consider having a new configuration
that extends the other ones. Although in most case I think the configurations themselves should
be fixed.
For instance in Eclipse you might want to resolve 3 kind of configurations: compile, test,
and runtime. And then you get the warning, because test and runtime conflicts on one dependency.
So this means that the ant target that will run the tests (after doing a resolve only on the
test configuration) will actually use a different version of a dependency from the one used
at runtime, from the one use by the ant target which build the jar. So tests are not running
in the same environment as the runtime one. Then you should fix the dependencies by having
a direct dependency on the module that generated the conflict. Actually you might want to
introduce a private "core" configuration, which will resolve the problematic dependency, and
then make "runtime" and "test" extends that "core" configuration.

The topic has been also discussed here :

> Duplidate entries after a resolve.
> ----------------------------------
>                 Key: IVY-810
>                 URL:
>             Project: Ivy
>          Issue Type: Bug
>    Affects Versions: 2.0.0-beta-2
>            Reporter: James Rosko
> I'm getting this error in the ivy console:
> "There are some duplicates entries due to conflicts between the resolved configurations
> and one dependent module is being picked up twice, two versions of the same project.
> I'm using the latest-revision conflict-manager.
> Project A has two dependencies that depend on different versions of a 4th project.  A
is getting both versions.   A depends on B and B depends on version 1 of D.  A also depends
on C and C depends on version 2 of D.  In this case A does not directly depend on D.  D is
not listed as a dependency of projects A's ivy.xml file.
> A->B->D1 and A->C->D2
> The problem does not occur when A directly depends on D
> A->D
> What could be causing this?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message