Hi, I have the following pom.xml
http://maven.apache.org/POM/4.0.0"; xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
com.proonto
platform-common
1.0
Proonto platform - common
Hello,
you need to exclude them from all direct dependencies which can drag it
in. For this the dependency:tree is a good tool. As you can see, it gets
dragged in by
org.springframework.data
spring-data-redis
Thanks, Jason.
Regards
Mirko
--
Sent from my mobile
On Jan 17, 2015 8:53 PM, "Jason van Zyl" wrote:
> Hi Mirko,
>
> I've raised a couple issues [1] and [2]. The first is likely not hard to
> implement so I'll take a look at that. We've had a couple requests for WAR
> support so if some more peo
Thanks Bernd,
I found that i mistakenly added the redis dependency twice,
so excluding dependencies on one did not exclude them from the other.
This is one of the mistakes that when you discover them you ask yourself
how didn't i notice that before.
On Sun, Jan 18, 2015 at 8:03 PM, Bernd Eckenfel
You might want to look at using Eclipse/STS (free) as your IDE.
Its support for Maven (m2e) is very useful and the dependency hierarchy
view would have solved this for you very quickly.
Ron
On 18/01/2015 3:45 PM, Yuval Zilberstein wrote:
Thanks Bernd,
I found that i mistakenly added the redis
It looks like I’ve accidentally ended up in a situation where I have
duplicate class names in separate .jars with different versions.
So I’ll have Foo.class in foo-1.0.0.jar and foo-3.0.0.jar …
Shouldn’t Maven fail in this scenario? IE assert that you have conflicting
dependencies and that you s
Check out
https://github.com/basepom/duplicate-finder-maven-plugin
On Jan 18, 2015, at 6:12 PM, Kevin Burton wrote:
> It looks like I’ve accidentally ended up in a situation where I have
> duplicate class names in separate .jars with different versions.
>
> So I’ll have Foo.class in foo-1.0.0.j
Hi,
if youre artifacts have the same artifactId/groupId/type/classifier it
should'nt happen,Maven should pick only one of the two. If one of
the artifactId/groupId/type/classifier is not the same, it could happen
because it's not the same jar for maven.
On Mon, Jan 19, 2015 at 4:32 AM, Steven S