maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raman Gupta (JIRA)" <j...@codehaus.org>
Subject [jira] (MENFORCER-118) DependencyConvergence gets better if it doesn't fail on snapshots of same baseVersion
Date Tue, 20 Mar 2012 06:26:02 GMT

    [ https://jira.codehaus.org/browse/MENFORCER-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=294579#comment-294579
] 

Raman Gupta commented on MENFORCER-118:
---------------------------------------

Is there a particular reason this change isn't being made?
                
> DependencyConvergence gets better if it doesn't fail on snapshots of same baseVersion
> -------------------------------------------------------------------------------------
>
>                 Key: MENFORCER-118
>                 URL: https://jira.codehaus.org/browse/MENFORCER-118
>             Project: Maven 2.x Enforcer Plugin
>          Issue Type: Improvement
>          Components: Standard Rules
>    Affects Versions: 1.0.1
>            Reporter: Poul Bilds√łe
>            Priority: Trivial
>
> The DependencyVersionMap used by DependencyConvergense uses node.getArtifact().getVersion()
when comparing versions. This makes the rule fail more often than needed because the version
compare doens't ignore the fact that some snapshots may have been resolved to timestamp. If
the code was node.getArtifact().getBaseVersion() instead then DependencyConvergense would
only fail on real version mismatches.

--
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

       

Mime
View raw message