[java-sig-commits] [Bug 1012059] jar file installed as pom, causes installation failure

bugzilla at redhat.com bugzilla at redhat.com
Fri Sep 27 07:01:18 UTC 2013


https://bugzilla.redhat.com/show_bug.cgi?id=1012059

Mikolaj Izdebski <mizdebsk at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|xmvn                        |maven-jar-plugin
           Assignee|sochotni at redhat.com         |msrb at redhat.com



--- Comment #5 from Mikolaj Izdebski <mizdebsk at redhat.com> ---
(In reply to Michal Srb from comment #4)
> In reproducer, you are binding both jar and war plugins to the same phase of
> a build lifecycle. Since jar plugin is executed after war plugin it sets the
> project's main artifact. You can try to run jar plugin in prepare-package
> phase (or explicitly specify maven-war-plugin after the jar plugin in your
> pom file). Only war file will be installed and I think it's a correct
> behavior. I don't consider it a bug in maven-jar-plugin. Reassigning back to
> XMvn.

My reproducer doesn't even use XMvn, so this has nothing to do with XMvn.

Multiple plugins can be bound to the same phase, that's not a problem. And this
problen is reproducible even if you bind JAR and WAR plugins to different
phases. This really is a problem in Maven JAR Plugin.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=wm3qrt2Ou0&a=cc_unsubscribe


More information about the java-sig-commits mailing list