Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (nike.apache.org: domain of stevenschlansker@gmail.com
 designates 209.85.192.176 as permitted sender)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Easy way to tell if I have .class file conflicts between two
 jars?
From: Steven Schlansker <stevenschlansker@gmail.com>
In-Reply-To: 
 <CAAZU44kbnFsTu7OK1dxmmUWUFBiW3fbSNwyO20rGocMPinN_9Q@mail.gmail.com>
Date: Mon, 6 Apr 2015 10:20:20 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <2CB638D9-EDCB-4072-8978-0E35C8FFB61A@gmail.com>
References: 
 <CAAZU44=pFahbSN=6Wd8RGO+okaxfShwXvGWAUkHNFeeYa-KREg@mail.gmail.com>
 <op.xwmstpcgkdkhrr@robertscholte.dynamic.ziggo.nl>
 <CAAZU44kbnFsTu7OK1dxmmUWUFBiW3fbSNwyO20rGocMPinN_9Q@mail.gmail.com>
To: Maven Users List <users@maven.apache.org>

I've been very happy with: =
https://github.com/basepom/duplicate-finder-maven-plugin

On Apr 5, 2015, at 11:59 AM, Kevin Burton <burton@spinn3r.com> wrote:

> Looks like it works but it=92s a little too strict. I just manually =
resolved
> some of the dependencies for one of my projects and it=92s complaining =
about
> conflicts even though the effective class path doesn=92t have those =
class
> conflicts.  hm.
>=20
> On Sun, Apr 5, 2015 at 11:11 AM, Robert Scholte <rfscholte@apache.org>
> wrote:
>=20
>> Hi,
>>=20
>> take a look at this enforcer rule:
>> =
http://mojo.codehaus.org/extra-enforcer-rules/banDuplicateClasses.html
>>=20
>> Robert
>>=20
>> Op Sun, 05 Apr 2015 19:57:07 +0200 schreef Kevin Burton <
>> burton@spinn3r.com>:
>>=20
>> Im looking for a somewhat easy way to tell if a directory of .jar =
files
>>> contains class reference which conflict.
>>>=20
>>> For example,org/xml/sax/XMLReader.class from two incompatible =
versions.
>>>=20
>>> I wrote a simple command that does a find and then a "jar tf" to =
list the
>>> contents, then I sort by the filename, but this creates false =
positives in
>>> the case where the files are actually the same .class file version.
>>>=20
>>> I think I could just use SHA1 to detect this =85 if the SHA1 is =
identical I
>>> can just ignore it.
>>>=20
>>> Of course a WAY better way to do this would be some sort of maven =
plugin
>>> that looked at all dependencies and generated errors/warnings if you =
add a
>>> dependency with class conflicts.  That would be sweet.
>>>=20
>>=20
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>=20
>>=20
>=20
>=20
> --=20
>=20
> Founder/CEO Spinn3r.com
> Location: *San Francisco, CA*
> blog: http://burtonator.wordpress.com
> =85 or check out my Google+ profile
> <https://plus.google.com/102718274791889610666/posts>
> <http://spinn3r.com>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org