I've a complicated Maven problem that I need help with and I'll try to explain it as best I can.
A few months ago, in work, I was working on a Java application which I built using Maven to manage its dependencies. I'm using Eclipse with an embedded version of Maven for development. We use TortoiseSVN as our source repository and I was doing all my development in a directory on my local machine (C:\), checking in my code after significant updates.
I've returned to the work after several months but due to directives from my employers all of our development now has to be done on a shared network drive. I've checked the project out of SVN to a location on my share drive but in Eclipse there are now several Java Build Path problems - several libraries that I've specified in the POM are missing. My initial guess was that, because I'm now working on a share drive, there's no longer any local Maven repository for the code to reference -- is that correct?
Working on a shared drive is a bad idea; checking out to a shared drive is so much slower because of network calls and such.
That said, Maven can function pointing at a shared drive (however slowly). It is just a drive after all. I think there are two possible causes of the problem here:
1) The local Maven repo moved. Was there a mandate for that to be on the shared drive too? If so, you'll need to update your settings.xml so Eclipse knows it moved.
2) A dependency used to be in the workspace and Eclipse is still looking for it there. Deleting it from the workspace could help (because then Maven will look at the repo). Or more likely starting building with the lower level projects first and then trying this project again when the lower level ones are succesful