Brian Fox wrote:
It will resolve the conflicts, but here no conflict exists from Maven's
point of view. The groupid is part of the coordinates so they appear to be
the same. Jdom should insert a "relocation" pom to solve these issues. Your
recourse is to use an exclusion.
Assuming the group was t
It will resolve the conflicts, but here no conflict exists from Maven's
point of view. The groupid is part of the coordinates so they appear to be
the same. Jdom should insert a "relocation" pom to solve these issues. Your
recourse is to use an exclusion.
Assuming the group was the same, you would
On Thu, May 7, 2009 at 1:10 PM, Ylan Segal wrote:
> I have a conflict with a jdom dependency: Two versions are appearing in my
> classpath.
>
> The problem arises because my project uses the follwing two dependencies:
>
>
>
> jdom
> jdom
> 1.1
>
>
> rome
> rom
I have a conflict with a jdom dependency: Two versions are appearing in
my classpath.
The problem arises because my project uses the follwing two dependencies:
jdom
jdom
1.1
rome
rome
0.9
Now, rome in turn uses:
jdom
jdom
