Eclipse: The archive which is referenced by the classpath, does not exist

Shengjie picture Shengjie · Mar 15, 2013 · Viewed 88.6k times · Source

My Eclipse is Indigo Java classic.

I have a java project which has mockito-all as a dependency. pom.xml:

<dependency>
    <groupId>org.mockito</groupId>
    <artifactId>mockito-all</artifactId>
    <version>1.8.5</version>
    <scope>test</scope>
</dependency>

run mvn clean install, everything is ok. Then I did mvn eclipse:eclipse to resolve all the dependencies in Eclipse.

when I try to run a Junit in eclipse, it doesn't run and gives me this error:

'Launching YourTest' has encountered a problem.

The archive: /home/shengjie/.m2/repository/org/mockito/mockito-all/1.9.5.jar which is referenced by the classpath, does not exist.

My project pom.xml claims it's depending on mockito-all 1.8.5, I am not sure where the 1.9.5 reference is coming from. Any ideas?

==EDIT==

$ mvn dependency:tree | grep mockito
[INFO] +- org.mockito:mockito-all:jar:1.8.5:test
[INFO] \- org.powermock:powermock-api-mockito:jar:1.4.12:test
[INFO] \- org.powermock:powermock-api-mockito:jar:1.4.12:test
[INFO]    +- org.mockito:mockito-all:jar:1.8.5:test (version managed from 1.9.0)
[INFO] |  +- org.mockito:mockito-all:jar:1.8.5:test (version managed from 1.9.5; scope managed from compile)
[INFO] |  +- org.mockito:mockito-all:jar:1.8.5:test (version managed from 1.9.5; scope managed from compile)
[INFO] \- org.powermock:powermock-api-mockito:jar:1.4.12:test
[INFO] +- org.mockito:mockito-all:jar:1.8.5:test
[INFO] +- org.powermock:powermock-api-mockito:jar:1.4.12:test
[INFO] |  +- org.mockito:mockito-all:jar:1.8.5:test (version managed from 1.9.5; scope managed from compile)

Answer

Birol Efe picture Birol Efe · Oct 8, 2013

I had a similar problem while I was trying to start my tomcat. I would suggest that you check "Classpath" the following way:

1) Run Configurations

  • Right click on your project
    • then click "Run" -> "Run Configurations..."
    • there check your settings for you project (e. g. in my case it was the Apache Tomcat)
    • here look into you tab "Classpath" under "User Entries"

2) Project classpath

  • Right click on your project -> "Properties" -> "Java Build Path"
    • now check the "Source" Tab as well as your "Libraries" Tab
    • Problems should be marked red in the "Libraries" tab