Feb 2nd, 2012, 11:47 AM
renaming local maven repository resolves multiple errors
I just resolved seemingly multiple errors with my project not being able to find Spring MVC org.aspectj.lang.JoinPoint not being on the classpath and what not, by renaming my maven repository to "older_repository".
Before this I tried with "-clean" and "-refresh" on the first two lines in the STS.ini file, and also "mvn clean install" and "mvn eclipse:clean eclipse:eclipse". None of this helped.
Now after I renamed the repository and again did clean install, all errors are gone and all tests run.
To my surprise there is no new repository folder inside ".m2" and maven seems to be finding the libraries some other way.
I've had loads of similar problems for the last year.
So why this situation? What's up with these kind of problems? Is the fault likely to be found within STS —after all there the errors are shown —, in Eclipse source, m2e, maven 3.x or somewhere else?
What do you guys think?
Tags for this Thread