Hi Chris,
my pom.xml looks like this [1]. The transformer you suggest is in place.
I think that it would help to not shade the test jar, but I'm using
shaded guava, which is bundled into core dependencies, so that might be
a little complicated. Possible, though.
This might be (maybe
Hi Jan,
are you using any of the shade transformers? We had similar problems in the
PLC4X project, but configuring:
Helped quite a bit.
Have a look here:
https://github.com/apache/plc4x/blob/develop/pom.xml#L1286
Hope this helps.
Chris
Am 03.12.19,
Hi Matt,
thanks for reaction. Is there a workaround around this? I think that the
PR I propose is "safe" and might be considered as a hotfix before a
proper solution is found? I don't know how is the release cycle of maven
plugins defined, but if there is an upcoming release soon, this might
Hi Jan,
See also https://github.com/apache/maven-shade-plugin/pull/14 and MSHADE-259
I stalled on it because it appears to be a lot of work to create unit tests for
maven plugins — and there weren’t examples to follow in the shade plugin.
That said, I’m not sure what I did is the right way to
Hi Maven :),
I encountered an exception in my build and I'm not sure if there is
something wrong with how I structure tasks in my pom.xml, or there is a
room for improvement of the shade plugin.
The symptoms are as follows:
- mvn install works just fine
- mvn deploy fails on 'duplicate
