[
https://jira.codehaus.org/browse/MENFORCER-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296120#comment-296120
]
Raman Gupta commented on MENFORCER-118:
---------------------------------------
Of course, the other question is: why does Maven resolve some snapshot
dependencies to a timestamped version, and others not? It seems to resolve
direct dependencies on "-SNAPSHOT" to a unique timestamped version, but
transitive dependencies to a non-unique version. Perhaps that is the real bug
that needs to be fixed?
> 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
