[
https://jira.codehaus.org/browse/MRESOURCES-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=275383#comment-275383
]
Haixing Hu edited comment on MRESOURCES-152 at 8/9/11 12:56 PM:
----------------------------------------------------------------
It seems related to this issue
http://jira.codehaus.org/browse/PLX-460
It's said that the bug has been fixed in version 1.5.6, but the
maven-resources-plugin depends on 1.0-alpha-9-stable-1
was (Author: starfish):
It seems related to this issue
http://jira.codehaus.org/browse/PLX-460
It is said to be fixed in version 1.5.6, but the maven-resources-plugin depends
on 1.0-alpha-9-stable-1
> The dependency of JUnit 3.8.1 may override the depended JUnit version of the
> project
> ------------------------------------------------------------------------------------
>
> Key: MRESOURCES-152
> URL: https://jira.codehaus.org/browse/MRESOURCES-152
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: Haixing Hu
> Priority: Blocker
>
> As the following pages state:
> http://maven.apache.org/plugins/maven-resources-plugin/dependencies.html
> The maven resources plugin itself depends on the JUnit 3.8.1, and any project
> using this plugin will be introduced a transitive dependency of JUnit 3.8.1.
> This will cause the projects which use JUnit 4.x in their unit test fail to
> pass the compilation under the command line (i.e., via "mvn install"), but
> they could be compiled under eclipse.
> I can't understand why this plugin has to introduce the dependency of Junit.
> Is it really necessary? If it is, could you please upgrade the JUnit to
> version 4 or above? Since JUnit 4.x provides a lot of assertArrayEquals(...)
> functions, which are really widely used.
> Thank you in advance.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
