[jira] (MENFORCER-123) BannedDependencies version number not taken into account

["Eric Duell (JIRA)" <ji...@codehaus.org>]

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

Eric Duell commented on MENFORCER-123:
--------------------------------------

Thanks a lot for the help. It took me quite a while until i came to this issue. Could you please update the documentation how to exclude a single version on your project page? http://maven.apache.org/enforcer/enforcer-rules/bannedDependencies.html

Examples:

* org.apache.maven
* org.apache.maven:badArtifact
* org.apache.maven:artifact:[badVersion]
* org.apache.maven:artifact:[badVersionRange)
* org.apache.maven:*:[1.2]
* org.apache.maven:*:*:jar:test
                
> BannedDependencies version number not taken into account
> --------------------------------------------------------
>
>                 Key: MENFORCER-123
>                 URL: https://jira.codehaus.org/browse/MENFORCER-123
>             Project: Maven 2.x Enforcer Plugin
>          Issue Type: Bug
>          Components: Standard Rules
>    Affects Versions: 1.1
>            Reporter: Arnout Engelen
>         Attachments: enforcer-explicitversion-test.patch
>
>
> When adding a rule with a specific version number (i.e. 'testGroupId:release:0.9'), it causes error messages for other versions of this artifact (i.e. 'testGroupId:release:jar:1.0').
> Attached is a patch agains enforcer-rules that adds a unit test demonstrating the problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira