[
http://jira.codehaus.org/browse/MCLIRR-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148807#action_148807
]
Jared Roberts commented on MCLIRR-15:
-------------------------------------
Sorry for the delayed response, I've been swamped with getting several projects
ready for release.
I've been unable to isolate exactly what is causing this. It consistently
happens in certain projects but I haven't been able to figure out what the
difference between the projects is so that I can recreate it in a simple
example. I suspected it might be old, invalid metadata, so I tried clearing the
snapshot repository as well as my local repository and that seems to fix some
projects and not others. I'm stumped and don't really have much time to commit
to this hunting the problem down right now. I do think there is still an issue,
I'm just not certain if it's an issue with the Clirr plugin or one of its
dependencies.
> 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
