You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Markus KARG (JIRA)" <ji...@codehaus.org> on 2012/08/20 15:31:21 UTC

[jira] (MJAR-159) JAR plugin must package again when POM is newer than JAR

Markus KARG created MJAR-159:
--------------------------------

             Summary: JAR plugin must package again when POM is newer than JAR
                 Key: MJAR-159
                 URL: https://jira.codehaus.org/browse/MJAR-159
             Project: Maven 2.x JAR Plugin
          Issue Type: Improvement
    Affects Versions: 2.4
            Reporter: Markus KARG


When the POM is modified (hence, when the JAR plugin's <manifest> or other artifact-modifying entries are modified), obviously it is necessary to package the JAR again to get this changes into the char (or at least, modify the existing JAR).

It feels rather odd to the user that when he does "mvn package", the JAR is not touched at all, while the manifest configuration is possibly completely changed!

As a solution, the JAR plugin should check whether the POM's file version is later than the JAR's file version and package then, even if there is no other change detected.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira