One such use has already been handled by the tycho-pack200a:normalize and
tycho-pack200b:pack goals.
They have to be used before and after jar:sign for pack200 to work, and
since the warning exists we have two plugins where you naively would expect
one.
But that is also the only use-case I've ever
It's probably the case where you haven't run mvn clean, so the shade plugin
finds the classes in the old already packaged jars in target.
Try to run mvn clean install, and if the warnings are still there, it's
something else...
/Andreas
--
View this message in context:
Now, I'm no export on annotation processors, but don't you have to have it
compiled before you can add it to the compiler arguments? In this, you say
to the compiler that it should use the class it's compiling as a processor
as well. That can't go well, can it?
/Andreas
--
View this message in
Stefano Nichele-2 wrote:
Hi All,
in my assembly file I have several fileSets sections and some of them
are used to copy some files under PATH/lib , others PATH/bin, others
in PATH/licenses. My issue is the I'd like to have PATH configured
just in one place and not replicated in all
After I upgraded to the latest m2eclipse the builds of out integration tests
started failing.
The reason was this:
I had set up our integration tests so that I could run one side of the
communication with an older version of our product (for compatibility
tests). I did this by setting up two
(Not sure if I should take this discussion here or to dev, so I play safe and
start here.)
I'm a currently happy user of maven that's learning about Java Web Start,
pack200, and signed jars. Seems that to be able to sign *and* pack200 a jar,
you need to repack it using pack200 *before* signing.
