[
http://jira.codehaus.org/browse/MEV-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128393#action_128393
]
Benjamin Bentmann commented on MEV-530:
---------------------------------------
bq. I don't want to be generating new sigs claiming that the pom.xml is good
without being able to tell if the pom.xml is good.
The POM in the repo is identical to the POM in the [tag for
2.0.6|http://svn.apache.org/viewvc/maven/components/tags/maven-2.0.6/pom.xml?revision=522714].
Jason added a one-line fix to this POM in
[r522714|http://svn.apache.org/viewvc?view=rev&revision=522714] after its
inital commit/deployment by the maven-release-plugin. Apparently the signatures
got not updated during the later redeploy, i.e. the checksums still match the
original POM from
[r522708|http://svn.apache.org/viewvc?view=rev&revision=522708].
> Broken checksum for org/apache/maven/maven/2.0.6/maven-2.0.6.pom
> ----------------------------------------------------------------
>
> Key: MEV-530
> URL: http://jira.codehaus.org/browse/MEV-530
> Project: Maven Evangelism
> Issue Type: Bug
> Reporter: Max Bowsher
> Assignee: Jason van Zyl
>
> org/apache/maven/maven/2.0.6/maven-2.0.6.pom has bad md5 and sha1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
