[
https://issues.apache.org/jira/browse/MJAR-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MJAR-159.
-------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> JAR plugin must package again when POM is newer than JAR
> --------------------------------------------------------
>
> Key: MJAR-159
> URL: https://issues.apache.org/jira/browse/MJAR-159
> Project: Maven 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 was sent by Atlassian JIRA
(v6.3.4#6332)
