[Yanel-dev] Re: [Dev] Maven repo dupes
Guillaume Déflache
guillaume.deflache at wyona.com
Wed Mar 31 10:26:23 CEST 2010
[This message just came on one internal Wyona mailing-lists, answering
it here as it is of general interest: ]
Mehmet Birgi schrieb:
> Yesterday, while we were looking for the jakarta-commons-io lib to
use, Guillaume noticed that this library is included twice, namely in:
>
>
/Users/memo/.m2/repository/apache-jakarta-commons/apache-jakarta-commons-io/1.2/apache-jakarta-commons-io-1.2.jar
> /Users/memo/.m2/repository/commons-io/commons-io/1.2/commons-io-1.2.jar
I previously found a statement in the jakarta-commons mailing-list about
what is the now recommended form (I do not really remember which one so
I won't risk a guess) and a rationale for it, I'll try to dig it up at home.
> As they are both the same version, one of them should be enough.
There may be other dupes, we didn't search for them. The bug
http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7006 also
seems to be remotely related to this. Would it be worth the effort to
It is indeed related to this. The cleanup explained below is made as
part of http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=6896
> try to clean out the maven repository? Or should I just enter a new P2
To sum it up is not really our or Maven's central repositories that are
"dirty", it's rather the dependencies metadata that do not cater for
renames of the groupId/artifactId couples during the life of a library.
Cleaning that would probably remove all "duplicate librairies", but it
is a long term task and not a very high priority ATM I think.
> bug and "forget about it" for now?
No need to enter another bug.
You can forget about it for now as an application developer as the only
real way to try to fix this is to clean up the dependency tree starting
from its "leaves".
For now only wyona-commons has been cleaned up (see r45585 on
<http://svn.wyona.com/repos/public/>), next target up the tree is yarep.
I had already started on that so please coordinate with us on this list
if you want to work on that.
HTH,
Guillaume
More information about the Yanel-development
mailing list