Jonny,

You will have to help us to investigate what is going on on your environment. Unfortunately information you provided is not sufficient to suggest you anything useful (you even didn't specified what m2eclipse version you are using and what Eclipse it is running on). Though from the error message you mentioned I can suspect that your installation is somehow messed up or broken and you can start from completely uninstalling m2eclipse and then do a clean install.

Another thing to note is that there is an issue in Maven (and that hasn't changed since May, so could not make m2eclipse releases any worse) so it goes for checking snapshots (based on update policy specified in your repository, e.g. it is worse if you use "always") or artifacts that don't have pom.xml in remote repositories. If some of your dependencies are like that, you can expect slow dependency resolution. In order to workaround that issue you can install local Maven repository manager, such as Sonatype Nexus or Artifactory. It will also speed up your command line build. See http://nexus.sonatype.org/

It would help, if you get a clean install, then use a clean Eclipse workspace and then try to reproduce your issues on small test project(s). Then if you can reproduce it there, submit a bug report and attach your project there with step by step instructions how to reproduce it along with information about your Eclipse configuration and all relevant logs and stack traces. You can find some hints on the wiki at http://docs.codehaus.org/display/M2ECLIPSE/Reporting+Issues

 Thanks

 Eugene


Jonny Cavell wrote:
Over the last few months I have lost days and days with this plugin.

Every version seems to introduce new bugs and new reasons why a Maven
project doesn't work in Eclipse. After I updated to the latest version, I
now get this error:

An internal error occurred during: "Updating Maven Dependencies".
org.maven.ide.eclipse.project.MavenProjectChangedEvent.getMavenProject()Lorg/maven/ide/eclipse/project/MavenProjectFacade;

What does that mean?

On a more general note, the biggest, ongoing issue that I have is that it
works ok for a while, and then I edit something, it starts updating the
dependencies (can take ages), and then suddenly cannot resolve imports, or
even classes from another project in the workspace (despite it being
configured to do so).

From the command line a mvn clean install works fine...

I really, really hate this plugin :(


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email


Reply via email to