[
https://jira.codehaus.org/browse/MRESOURCES-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=275448#comment-275448
]
Haixing Hu commented on MRESOURCES-152:
---------------------------------------
Oh my god!
It's so strange. I just recompiled the porject again and was surprised to found
that the porject passed the compilation! But I swear it was not got compiled
yeasterday.
I remember that the only thing I have done is to remove all my "~/.m2"
directory and force the maven to downloads all dependency again.
Maybe some conflicts of dependency caused that problem.
Anyway, the good news is that my project got compiled, and the bad news is that
the protential bug may still exist and I can't reproduce it.
So I close this issue.
> 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
