Re: Duplicate plugin declaration warning
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 seen... /Andreas -- View this message in context: http://maven.40175.n5.nabble.com/Duplicate-plugin-declaration-warning-tp5820730p5821591.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Shade Plugin issues thousands of [WARNING] we have a duplicate
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: http://maven.40175.n5.nabble.com/Shade-Plugin-issues-thousands-of-WARNING-we-have-a-duplicate-tp5716181p5716187.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Need help with a dependency problem...
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 context: http://maven.40175.n5.nabble.com/Need-help-with-a-dependency-problem-tp3280645p3280922.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: properties in assembly plugin
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 /lib , others /bin, others
> in /licenses. My issue is the I'd like to have configured
> just in one place and not replicated in all fileSets sections.
>
> Is there a way to set in once in the assembly file or in the pom.xml as
> configuration property ?
>
> Thanks in advance
> ste
>
Well, I reference ${project.build.directory} with no problems in my
assembly.xml, so you should just be able to define a property in your pom
and go with it.
Does that not work?
/Andreas
--
View this message in context:
http://old.nabble.com/properties-in-assembly-plugin-tp27767079p27767294.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Maven 3 incompatiblity
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 dependencies for the same artifact,
with different scopes (compile and runtime). (See example below)
This failed in Maven 3, the error message was that I had two dependencies
with the same version.
Now, I solved my problem by changing the setup of the tests from using
copy-dependencies to using copy (and all the dependencies spelled out in the
configuration). But the previous solution was nicer, in that copy-dependecy
also brought with it the transitive dependencies as well. Now I had to
duplicate 'em by hand instead.
Question: is this intended behavior? Or should the version check look at the
scope as well?
Example:
com.example
component
${client-side-version}
compile
com.example
component
${server-side-version}
runtime
The jars are copied with maven-dependency-plugin:copy-dependency.
When a developer builds client- and server-side-version are the same. During
compatiblility tests one is pointed to the previous version.
--
View this message in context:
http://old.nabble.com/Maven-3-incompatiblity-tp26492785p26492785.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Idea for extension of maven-jarsigner-plugin
(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. And I think that the perfect place to be able to do this is in the jarsigner plugin, via a new option. Now, I'm perfectly happy with creating a patch for this myself, but it might just be something that others might be interested as well. Thoughts, comments? /Andreas -- View this message in context: http://www.nabble.com/Idea-for-extension-of-maven-jarsigner-plugin-tp25530562p25530562.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
