[
http://jira.codehaus.org/browse/MCLIRR-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144323#action_144323
]
Jared Roberts commented on MCLIRR-15:
-------------------------------------
No I'm not using any proxies. This issue appears to be related to
maven-metadata.xml on the remote repository containing a
"metadata/versioning/snapshot/timestamp" node. The projects that fail contain
this node. One of the projects was originally deployed with Maven 2.0.7, so
that's a place to start looking. I've been searching for Maven bugs that have
been fixed and stumbled across MNG-2780 and MNG-1908.
> Uniquely versioned snapshots are not ignored
> --------------------------------------------
>
> Key: MCLIRR-15
> URL: http://jira.codehaus.org/browse/MCLIRR-15
> Project: Maven 2.x Clirr Plugin
> Issue Type: Bug
> Affects Versions: 2.2.2
> Reporter: Jared Roberts
> Attachments: MCLIRR-15-clirr-maven-plugin.patch
>
>
> Unique versions of snapshots are being seen as the previous release artifact
> for comparison. For example, throughout development, the Clirr report shows
> the comparison between artifact-2.0-SNAPSHOT and
> artifact-2.0-20080804.224602-1. The current workaround is to configure the
> "comparisonVersion" or "comparisonArtifacts" in the POM.
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
