[
https://jira.codehaus.org/browse/MNG-5096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=273275#comment-273275
]
Martin Grotzke commented on MNG-5096:
-------------------------------------
I just found out that with maven 3 (tested with 3.0.2) changing
{{<type>test-jar</type>}} to {{<classifier>tests</classifier>}} solves this
issue. With maven 2 (tested with 2.2.1) the situation is still the same.
> <exclusion> on <dependency> with <type>test-jar</type> doesn't work in maven 3
> ------------------------------------------------------------------------------
>
> Key: MNG-5096
> URL: https://jira.codehaus.org/browse/MNG-5096
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects Versions: 3.0.3
> Environment: Ubuntu 10.04
> Reporter: Garrett Wu
> Attachments: maven-testcase.tar.gz
>
>
> There appears to be a regression in maven 3 that breaks test-jar dependency
> exclusions. I've attached a simple example to reproduce this. There are two
> projects: foo and bar. Project foo produces a test-jar artifact. Project
> bar depends on foo's test-jar but excludes a dependency on junit. In maven
> 2, a dependency:list shows that junit has successfully been excluded. In
> maven 3, a dependency:list shows that junit was not successfully excluded.
> To reproduce, download the {{maven-testcase.tar.gz}} attachment and run:
> {code:none}
> $ tar xzvf maven-testcase.tar.gz
> $ cd maven-testcase/foo
> $ mvn2 install
> $ cd ../bar
> $ mvn2 dependency:list
> ...
> [INFO] The following files have been resolved:
> [INFO] org.apache.maven:foo:test-jar:tests:1.0:test
> ...
> $ mvn3 dependency:list
> ...
> [INFO] The following files have been resolved:
> [INFO] junit:junit:jar:4.8.1:test
> [INFO] org.apache.maven:foo:test-jar:tests:1.0:test
> ...
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
