Hi,
We have a pom.xml for the drools guvnor repository jar, with this
identification:
<groupId>org.drools</groupId>
<artifactId>drools-repository</artifactId>
<version>5.1.0</version>
Now, for the next version of that jar, we need to change the
identification to:
<groupId>org.drools.guvnor</groupId>
<artifactId>guvnor-repository</artifactId>
<version>5.2.0</version>
It's the same code in the jar, but the original identification was wrong
and we're fixing that now.
The problem is, what happens if one of our users has this dependency tree?
- foo
-- foo depends on bar
--- bar depends on org.drools:drools-repository:5.1.0
-- foo depends on org.drools.guvnor:guvnor-repository:5.2.0
Maven will not detect the dependency conflict between
- org.drools:drools-repository:5.1.0
- org.drools.guvnor:guvnor-repository:5.2.0
and it will put both of them in the classpath, instead of just 5.2.0.
Is there any way to tell maven in the 5.2.0 pom.xml, something like this:
<groupId>org.drools.guvnor</groupId>
<artifactId>guvnor-repository</artifactId>
<version>5.2.0</version>
<legacy-identifications>
<legacy-identification>
<groupId>org.drools</groupId>
<artifactId>drools-repository</artifactId>
<legacy-identification>
</legacy-identifications>
So it does detect the dependency conflict and lets just 5.2.0 survive?
--
With kind regards,
Geoffrey De Smet
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
