Re: [m2e-dev] [m2eclipse-dev] Maven integration in Indigo

[Igor Fedorenko <igor@xxxxxxxxxxxxxx>]

There are updated compatible versions of some m2e-extras, but we are
working on m2e-core APIs and picking matching builds of all components
is not easy. Things should settle down after 0.13.0 M6. In the mean
time, you can install reasonably recent m2e 0.13.0 from [1].

[1] https://www.sonatype.com/~ifedorenko/m2e4m2e/

--
Regards,
Igor

On 11-02-16 07:56 AM, Julien HENRY wrote:
> Hi,
>
> I'm testing integration of m2eclipse in the coming Eclipse indigo release. I'm
> currently using M5 build.
>
> After importing my projects I got a first error about m-resources-p being too
> old for m2eclipse. Nice addition!
>
> After upgrading m-resources-p in my corporate pom I had another error: something
> about build helper plugin not mapped to custom lifecycle. This is another nice
> addition that make me understand that I needed "Project configurators for some
> commonly used maven plugins" which was previously available in extras update
> site. I tried to use latest version available and I have downloaded
> org.sonatype.m2e.site-extras-0.13.0-20110214.191126-15-site.zip on your Nexus
> instance. The installation was fine (no error about version incompatibility),
> but after restarting Eclipse and trying to update Maven configuration on a
> project, I received the following error:
>
> java.lang.NoSuchMethodError:
> org.sonatype.m2e.mojos.internal.AbstractJavaProjectConfigurator.getMojoExecutions(Lorg/eclipse/m2e/core/project/configurator/ProjectConfigurationRequest;Lorg/eclipse/core/runtime/IProgressMonitor;)Ljava/util/List;
>
> at
> org.sonatype.m2e.mojos.internal.AbstractJavaProjectConfigurator.configureRawClasspath(AbstractJavaProjectConfigurator.java:53)
>
> at
> org.eclipse.m2e.jdt.internal.AbstractJavaProjectConfigurator.invokeJavaProjectConfigurators(AbstractJavaProjectConfigurator.java:170)
>
> at
> org.eclipse.m2e.jdt.internal.AbstractJavaProjectConfigurator.configure(AbstractJavaProjectConfigurator.java:113)
>
> at
> org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:59)
>
> at
> org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:324)
>
> at
> org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:305)
>
> at
> org.eclipse.m2e.core.actions.UpdateConfigurationAction$1.runInWorkspace(UpdateConfigurationAction.java:104)
>
> at
> org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
>
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
>
>
> I guess this is because "Project configurators for some commonly used maven
> plugins." was not migrated to use new API of eclipse-hosted m2eclipse. Is there
> anything I can do to fix the situation and make my project usable? Is it planned
> to host "extras" at Eclipse or will it stay an external project with an external
> update site?
>
> Regards,
>
> Julien