blocks|key|912992|text|@Dennis+Roberts:你完全正确:我的测试类位于src/main/java中。此外，JUnit的POM中的"scope“元素的值是"test"，尽管它应该是这样的。问题是我在Eclipse中创建测试类时很草率，导致它被创建在src/+test+/java的src/main/java实例中。在运行"mvn+eclipse:eclipse“之后，在eclipse的Project+Explorer视图中可以很容易地看到这一点，但正是您的注释让我最先看到了它。谢谢。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|912993|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

@Dennis Roberts: You were absolutely right: My test class was located in src/main/java. Also the value of the "scope" element in the POM for JUnit was "test", although that is how it is supposed to be. The problem was that I had been sloppy when creating the test class in Eclipse, resulting in it being created in src/main/java insted of src/test/java. This became easier to see in Eclipse's Project Explorer view after running "mvn eclipse:eclipse", but your comment was what made me see it first. Thanks.

blocks|key|913205|text|只是为了得到一个完整的解决方案的答案来帮助访问者：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|913206|您需要做的就是将junit依赖项添加到pom.xml。别忘了<scope>test</scope>|offset|length|style|CODE|913207|<dependency>
++<groupId>junit</groupId>
++<artifactId>junit</artifactId>
++<version>4.11</version>
++<scope>test</scope>
</dependency>|code-block|syntax|javascript|913208|entityMap^0|0|J|7|U|J|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@$D|Q|E|R|F|G]|$D|S|E|T|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|U|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

Just to have an answer with the complete solution to help the visitors:

All you need to do is add the junit dependency to <code>pom.xml</code>. Don't forget the <code>&lt;scope&gt;test&lt;/scope&gt;</code>

<pre><code>&lt;dependency&gt;
 &lt;groupId&gt;junit&lt;/groupId&gt;
 &lt;artifactId&gt;junit&lt;/artifactId&gt;
 &lt;version&gt;4.11&lt;/version&gt;
 &lt;scope&gt;test&lt;/scope&gt;
&lt;/dependency&gt;
</code></pre>

blocks|key|913277|text|我的问题是我的pom.xml中有一行，我有<sourceDirectory>${basedir}/src</sourceDirectory>这一行，删除这一行，让maven使用常规结构的文件夹，这解决了我的问题|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|913278|entityMap^0|7|7|L|1D|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

my problem was a line inside my <code>pom.xml</code> i had the line <code>&lt;sourceDirectory&gt;${basedir}/src&lt;/sourceDirectory&gt;</code> removing this line made maven use regular structure folders which solves my issue

blocks|key|697261|text|删除junit的pom.xml中的作用域标记起作用了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|697262|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

removing the scope tag in pom.xml for junit worked..

blocks|key|697121|text|我也有同样的问题。我所做的就是-从pom.xml文件中删除JUnit3.8的依赖项，并为JUnit4.8添加一个新的依赖项。然后我做了maven清理和maven安装。它做到了这一点。为了验证，在maven安装之后，我转到project->properties-build+path->maven+dependencies，看到现在junit+3.8jar已经不存在了，而是列出了junit+4.8jar。酷！！.现在我的测试运行起来像个魔咒..希望这能有所帮助..|type|unstyled|depth|inlineStyleRanges|entityRanges|data|697122|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same problem. All i did was - From the pom.xml file i deleted the dependency for junit 3.8 and added a new dependency for junit 4.8. Then i did maven clean and maven install. It did the trick. To verify , after maven install i went project->properties-build path->maven dependencies and saw that now the junit 3.8 jar is gone !, instead junit 4.8 jar is listed. cool!!. Now my test runs like a charm.. Hope this helps somehow..

blocks|key|697198|text|将此依赖项添加到pom.xml文件：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|697199|http://mvnrepository.com/artifact/junit/junit-dep/4.8.2|697200|
<dependency>
++++<groupId>junit</groupId>
++++<artifactId>junit-dep</artifactId>
++++<version>4.8.2</version>
</dependency>|code-block|syntax|javascript|697201|entityMap|0|LINK|mutability|MUTABLE|url^0|8|7|0|0|1J|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@]|D|@$9|X|A|Y|1|Z]]|E|$]]|$1|H|3|I|5|J|7|10|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|G]]]]

Add this dependency to your <code>pom.xml</code> file:

<a href="http://mvnrepository.com/artifact/junit/junit-dep/4.8.2" rel="nofollow noreferrer">http://mvnrepository.com/artifact/junit/junit-dep/4.8.2</a>

<pre><code>&lt;!-- https://mvnrepository.com/artifact/junit/junit-dep --&gt;
&lt;dependency&gt;
 &lt;groupId&gt;junit&lt;/groupId&gt;
 &lt;artifactId&gt;junit-dep&lt;/artifactId&gt;
 &lt;version&gt;4.8.2&lt;/version&gt;
&lt;/dependency&gt;
</code></pre>

blocks|key|913582|text|我的案子只是个简单的疏忽。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|913583|我将JUnit依赖声明放在<dependencies>中的<dependencyManagement/>节点下，而不是POM文件中的<project/>。正确的方法是：|offset|length|style|CODE|913584|<project>

++++<dependencies>
++++
++++++++<dependency>
++++++++++++<groupId>junit</groupId>
++++++++++++<artifactId>junit</artifactId>
++++++++++++<version>4.11</version>
++++++++</dependency>
++++</dependencies>
<project>|code-block|syntax|javascript|913585|entityMap^0|0|D|E|T|N|1U|A|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@$D|Q|E|R|F|G]|$D|S|E|T|F|G]|$D|U|E|V|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|W|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|N|$]]

My case was a simple oversight.

I put the JUnit dependency declaration inside <code>&lt;dependencies&gt;</code> under the <code>&lt;dependencyManagement/&gt;</code> node instead of <code>&lt;project/&gt;</code> in the POM file. Correct way is:

<pre><code>&lt;project&gt;
&lt;!-- Other elements --&gt;
 &lt;dependencies&gt;
 &lt;!-- Other dependencies--&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;junit&lt;/groupId&gt;
 &lt;artifactId&gt;junit&lt;/artifactId&gt;
 &lt;version&gt;4.11&lt;/version&gt;
 &lt;/dependency&gt;
 &lt;/dependencies&gt;
&lt;project&gt;
</code></pre>

blocks|key|697444|text|我将文件放在了正确的位置，只需从JUnit依赖项中删除<scope>test</scope>就解决了这个问题(我使用的是JUnit+4.12)。我相信对于test作用域，依赖项只是在编译阶段被忽略了。现在，即使当我调用mvn+test时，一切都可以正常工作。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|697445|entityMap^0|R|J|25|4|31|8|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

I had my files at the correct places, and just removing <code>&lt;scope&gt;test&lt;/scope&gt;</code> from the JUnit dependency entry solved the problem (I am using JUnit 4.12). I believe that with the <code>test</code> scope the dependency was just being ignored during the compilation phase. Now everything is working even when I call <code>mvn test</code>.

blocks|key|697516|text|我在注入依赖的父项目的"test-utils“项目(向JUnit添加特性、规则和断言)子项目中遇到了一个非常类似的问题。依赖于org.junit.rules包的类位于src/main/java中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|697517|所以我在没有测试作用域的junit上添加了一个依赖项，它解决了这个问题：|697518|测试用例项目的pom.xml：|697519|<dependency>
++<groupId>junit</groupId>
++<artifactId>junit</artifactId>
</dependency>|code-block|syntax|javascript|697520|父项目的pom.xml：|697521|<dependency>
++<groupId>junit</groupId>
++<artifactId>junit</artifactId>
++<scope>test</scope>
</dependency>|697522|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|T|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|V|8|@]|9|@]|A|$I|J]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I had a quite similar problem in a "test-utils" project (adding features, rules and assertions to JUnit) child of a parent project injecting dependencies.
The class depending on the org.junit.rules package was in src/main/java.

So I added a dependency on junit without test scope and it solved the problem :

pom.xml of the test-util project :

<pre><code>&lt;dependency&gt;
 &lt;groupId&gt;junit&lt;/groupId&gt;
 &lt;artifactId&gt;junit&lt;/artifactId&gt;
&lt;/dependency&gt;
</code></pre>

pom.xml of the parent project :

<pre><code>&lt;dependency&gt;
 &lt;groupId&gt;junit&lt;/groupId&gt;
 &lt;artifactId&gt;junit&lt;/artifactId&gt;
 &lt;scope&gt;test&lt;/scope&gt;
&lt;/dependency&gt;
</code></pre>

blocks|key|697595|text|我也有同样的问题，如下所示。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|697596|​|697597|📷|atomic|offset|length|697598|697599|要解决此问题，请将以下行添加到应用程序级别build.gradle中的dependencies部分。|style|CODE|697600|compile+'junit:junit:4.12'
androidTestCompile+'com.android.support.test:runner:0.5'|code-block|syntax|javascript|697601|Gradle+build随后报告了以下警告。|697602|Warning:Conflict+with+dependency+'com.android.support:support-annotations'.+
Resolved+versions+for+app+(25.1.0)+and+test+app+(23.1.1)+differ.+
See+http://g.co/androidstudio/app-test-app-conflict+for+details.|697603|要解决此警告，请在应用程序级别的build.gradle中添加以下部分。|697604|configurations.all+{
++++resolutionStrategy+{
++++++++force+'com.android.support:support-annotations:23.1.1'
++++}
}|697605|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/8c1b2e65940802fd6e878e8aafe740ef.png|imageAlt^0|0|0|0|1|0|0|0|Z|C|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|19|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1A|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1B|8|@]|9|@$G|1C|H|1D|1|1E]]|A|$]]|$1|I|3|C|5|6|7|1F|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1G|8|@$G|1H|H|1I|L|M]]|9|@]|A|$]]|$1|N|3|O|5|P|7|1J|8|@]|9|@]|A|$Q|R]]|$1|S|3|T|5|6|7|1K|8|@]|9|@]|A|$]]|$1|U|3|V|5|P|7|1L|8|@]|9|@]|A|$Q|R]]|$1|W|3|X|5|6|7|1M|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|P|7|1N|8|@]|9|@]|A|$Q|R]]|$1|10|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]]|11|$12|$5|13|14|15|A|$16|17|18|-4]]]]

Me too had the same problem as shown below.

<a href="https://i.stack.imgur.com/t4RlY.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/t4RlY.png" alt="enter image description here"></a>

To resolve the issue, below lines are added to <code>dependencies</code> section in the app level build.gradle.

<pre><code>compile 'junit:junit:4.12'
androidTestCompile 'com.android.support.test:runner:0.5'
</code></pre>

Gradle build then reported following warning. 

<pre><code>Warning:Conflict with dependency 'com.android.support:support-annotations'. 
Resolved versions for app (25.1.0) and test app (23.1.1) differ. 
See http://g.co/androidstudio/app-test-app-conflict for details.
</code></pre>

To solve this warning, following section is added to the app level build.gradle.

<pre><code>configurations.all {
 resolutionStrategy {
 force 'com.android.support:support-annotations:23.1.1'
 }
}
</code></pre>

blocks|key|913085|text|我在Eclipse编译我的代码时遇到了类似的问题，但是每次编译测试时都会失败，尽管JUnit在我的依赖项列表中，并且测试在/src/test/java/中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|913086|在我的例子中，我的依赖项列表中有错误的JUnit版本。我编写了JUnit4测试(带注释)，但使用JUnit+3.8.x作为我的依赖项。在JUnit的3.8.x和4版本之间，他们将包名称从junit.framework更改为org.junit，这就是为什么Maven仍然无法使用JUnit+jar进行编译。|913087|我仍然不能完全确定Eclipse成功编译的原因。它必须在类路径中的某个位置拥有自己的JUnit4副本。希望这个替代解决方案对人们有用。我是通过上面的Arthur链接得到这个解决方案的。|913088|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I had a similar problem of Eclipse compiling my code just fine but Maven failed when compiling the tests every time despite the fact JUnit was in my list of dependencies and the tests were in /src/test/java/.

In my case, I had the wrong version of JUnit in my list of dependencies. I wrote JUnit4 tests (with annotations) but had JUnit 3.8.x as my dependency. Between version 3.8.x and 4 of JUnit they changed the package name from junit.framework to org.junit which is why Maven still breaks compiling using a JUnit jar.

I'm still not entirely sure why Eclipse successfully compiled. It must have its own copy of JUnit4 somewhere in the classpath. Hope this alternative solution is useful to people. I reached this solution after following Arthur's link above.

blocks|key|697377|text|我也遇到了这个问题-我试图从源代码中拉入一个对象，但它在测试代码中工作正常，但在src代码中却不起作用。为了进一步测试，我从测试中复制了一段代码，并将其放入src代码中，然后立即删除了JUnit行，这样我就知道了测试是如何引入对象的。突然我的代码就不能编译了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|697378|问题是，当我把代码放进去时，Eclipse很有帮助地解决了所有的类，所以我的src代码有JUnit调用，这是不正确的。我应该注意到顶部关于未使用的导入的警告，但我忽略了它们。|697379|一旦我在我的src文件中删除了未使用的JUnit导入，它就能很好地工作。|697380|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I also ran into this issue - I was trying to pull in an object from a source and it was working in the test code but not the src code. To further test, I copied a block of code from the test and dropped it into the src code, then immediately removed the JUnit lines so I just had how the test was pulling in the object. Then suddenly my code wouldn't compile. 
The issue was that when I dropped the code in, Eclipse helpfully resolved all the classes so I had JUnit calls coming from my src code, which was not proper. I should have noticed the warnings at the top about unused imports, but I neglected to see them. 
Once I removed the unused JUnit imports in my src file, it all worked beautifully.

blocks|key|913736|text|如果您在src/main/java+Utils中有代码，请找到此错误的一个解决方案|type|unstyled|depth|inlineStyleRanges|entityRanges|data|913737|<dependency>
<groupId>org.assertj</groupId>
<artifactId>assertj-core</artifactId>
<version>3.9.1</version>
</dependency>|code-block|syntax|javascript|913738|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Find the one solution for this error if you have code in src/main/java Utils

<pre><code>&lt;dependency&gt;
&lt;groupId&gt;org.assertj&lt;/groupId&gt;
&lt;artifactId&gt;assertj-core&lt;/artifactId&gt;
&lt;version&gt;3.9.1&lt;/version&gt;
&lt;/dependency&gt;
</code></pre>

blocks|key|697695|text|更改junit版本为我修复了这个问题。似乎3.8.1版在我的情况下不起作用。将其更改为4.12后修复的问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|697696|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Changing the junit version fixed this for me. Seems like version 3.8.1 didn't work in my case. Issue fixed upon changing it to 4.12

blocks|key|697292|text|缺省情况下，maven分别在这些文件夹中查找java和test类src/main/java和src/test/java。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|697293|当src被指定为源代码下的测试类，并且pom.xml中junit依赖的范围被提到为test+-+org.unit时，maven将找不到它。|697294|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

By default , maven looks at these folders for java and test classes respectively -
src/main/java and src/test/java

When the src is specified with the test classes under source and the scope for junit dependency in pom.xml is mentioned as test - org.unit will not be found by maven.

I am trying to build a simple Java project with Maven. In my pom-file I declare JUnit 4.8.2 as the only dependency. Still Maven insists on using JUnit version 3.8.1. How do I fix it?

The problem manifests itself in a compilation failure: "package org.junit does not exist". This is because of the import statement in my source code. The correct package name in JUnit 4.* is org.junit.* while in version 3.* it is junit.framework.*

I think I have found documentation on the root of the problem on <a href="http://maven.apache.org/plugins/maven-surefire-plugin/examples/junit.html" rel="noreferrer">http://maven.apache.org/plugins/maven-surefire-plugin/examples/junit.html</a> but the advice there seems to be meant for Maven experts. I did not understand what to do.

Maven 3 and JUnit 4 compilation problem: package org.junit does not exist

我正在尝试使用Maven构建一个简单的Java项目。在我的pom-file中，我声明JUnit 4.8.2是唯一的依赖项。尽管如此，Maven仍然坚持使用JUnit版本3.8.1。我该如何修复它？问题表现为编译失败："package org.junit不存在“。这是因为我的源代码中的import语句。在JUnit 4.*中，正确的包名是org.junit.*，而在版本3.*中，它是Junit.fr

问org.junit 3和Maven 4编译问题:包Maven不存在
EN

回答 15

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问org.junit 3和Maven 4编译问题:包Maven不存在EN

回答 15

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问org.junit 3和Maven 4编译问题:包Maven不存在
EN