With recent version of m2eclipse (0.12.1.20110112-1712) I am facing really weird problems with artifact resolutions. the project is building just fine with command-line. The artifacts do really exist in local maven repository.
I tried to
- enable/disable dependency management
- update project configuration
- update dependencies
- not using embedded maven 3.0 but use external maven 2.2.1
- use different JDK in eclipse.ini
- voodoo magic
but nothing helps.
Please suggest what else may I try or some replacement for this plugin.
you could uninstall m2eclipse and use the eclipse:eclipse plugin for maven instead. This will generate/update your .project and .classpath files for you. Then, when your pom changes, you just run mvn eclipse:eclipse again to update them.