If you copy an Eclipse-Maven project from one computer to another, you may get a Build Path Problem resembling: "The container 'Maven Dependencies' references non existing library 'XXXXXXXXXXXX'". This is obviously due to a difference in the location of the local Maven repository from one computer to the other.
To fix this, right-click on the project > Maven > Disable Dependency Management. Once Eclipse has finished rebuilding the project, right-click on the project > Maven > Enable Dependency Management. This error should now be gone.
Labels
.net
(1)
*nix
(1)
administration
(1)
Android
(2)
Axis2
(2)
best practice
(5)
big-data
(1)
business-analysis
(1)
code re-use
(1)
continuous-integration
(1)
Cordova-PhoneGap
(1)
database
(2)
defect
(1)
design
(3)
Eclipse
(7)
education
(1)
groovy
(2)
https
(2)
Hudson
(4)
Java
(1)
JAX-RS
(2)
Jersey
(3)
Jetty
(1)
localization
(1)
m2eclipse
(2)
MapForce
(1)
Maven
(12)
MySQL
(1)
Nexus
(4)
notes
(4)
OO
(1)
Oracle
(4)
performance
(1)
Perl
(1)
PL/SQL
(1)
podcast
(1)
PostgreSQL
(1)
requirement
(1)
scripting
(1)
serialization
(1)
shell
(1)
SoapUI
(1)
SQL
(1)
SSH
(2)
stored procedure
(1)
STS
(2)
Subclipse
(1)
Subversion
(3)
TOAD
(3)
Tomcat
(4)
UML
(2)
unit-testing
(2)
WAMP
(1)
WAS
(3)
Windows
(3)
WP8
(2)
WTP
(2)
XML
(4)
XSLT
(1)
Subscribe to:
Post Comments (Atom)
i have this blocking problem :
ReplyDeleteHow can i disable the dependency management ; i'm using eclipse kepler.
this will be e great help
The container 'Maven Dependencies' references non existing library 'C:\Users\dev\.m2\repository\org\modeshape\modeshape-common\3.7-SNAPSHOT\modeshape-common-3.7-SNAPSHOT.jar' modeshape-webdav Build path Build Path Problem