If I update a dependency (to a new version not yet in my local repo) in my
pom and then save it, then eclipse shows the "Update Maven Dependencies" for
a short while, but no artifact is downloaded and the project is shown with
an error as "Missing artifact bla bla" in eclipse!
But if I choose "Run as-Maven package" on the project, then it executes
maven externally and THEN downloads it without any problem at all!
After that I just have to re-do Maven->Update Dependencies and then the
project errors dissapear?!?

It should be mentioned that I due to earlier recommendations (on this
mailing list) I am my external maven installation instead of using the
embedded maven, but these use the same macen settings.xml!!
(C:\Users\<myuser>\.m2\settings.xml in Vista)

The thing is that I am pretty sure this worked properly before, maybe in a
previous version of m2eclipse, but not sure...

//Kent

Reply via email to