Yaron is right: you may find problems in your build by NOT moving the .m2/repository folder. You may discover that specific files were available only in your local repo and not anywhere else (Maven Central or your local proxy such as Archiva/Artifactory/Nexus). And this is a good time to discover bad practise in your build. But the answer to the original question is YES, simply copy the directory .m2/repository and inspect any specific setting in .m2/settings.xml.
-- Sent from: http://maven.40175.n5.nabble.com/Maven-Users-f40176.html --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
