Hi,
As far as I know this is not supported by the assembly-plugin directly.
If the two jars contain exactly the same set of classes (just different
versions) you can just exclude one of them via the <excludes/> tag. Or
you can try to define two distinct <dependencySet> respectivly
<moduleSet/> definitions. One containing the dependencies pulling in
A.jar, one with the dependencies pulling in B.jar and then try to switch
the order of the two definitions in your assembly descriptor and hope
that that switches the order in which the jars get copied.
-Tim
aldana schrieb:
hi,
i am facing following problem:
when building assembly there are two libraries (A.jar+B.jar) which contain
same classes (packageName + className). looking at this library A.jar
contains a class which offers different public methods as B.jar. assembly
plugin now overrides this A.jar class with B.jar classes.
result of this, that application gives me a NotSuchMethodException.
unfortunately i cannot replace A with B or otherwise. both need to be
assembled into one jar.
so how is it possible to configure following in assembly plugin:
-dependency X defined in pom.xml of project P1 should be preferred over
dependency Y in pom.xml of project P2, when running assembly:assembly
thanks in advance!
besides: i know i should change my architecture to avoid such a library
conflict (there should exist only one class version). but before refactoring
i need a quick solution to make a running release.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
