Actually, perhaps the embedded Maven just got in a messed up state. I restarted eclipse and the error went away.
The new WTP version works for me. Mike On Thu, Apr 14, 2011 at 4:16 PM, Michael Youngstrom <[email protected]> wrote: > I upgraded to the latest 0.12 build to help test and I am now getting > a new error that may or may not be related. > > Environment > Helios 3.6.2 > m2e 0.12.1.20110112-1712 > m2e-wtp 0.12.0.201104141036 > > I am getting the following error in one of my poms: > > Description Resource Path Location Type > Guice provision errors: > > 1) No implementation for org.apache.maven.plugin.Mojo annotated with > @Named(value=org.apache.maven.plugins:maven-resources-plugin:2.5:resources) > was bound. > > 1 error pom.xml /svn-rm-deploy line 1 Maven Problem > > I've never seen this error before I upgraded to m2e-wtp > 0.12.0.201104141036. The previous m2e-wtp version I was using was > 0.12.0.201101121522. > > This appears to be caused because I am using the > org.maven.ide.eclipse:lifecycle-mapping plugin to only execute the > "maven-resources-plugin". Thoughts? Could your recent change have > caused this? Here is my profile snippet: > > <profiles> > <profile> > <id>m2e</id> > <activation> > <property> > <name>m2e.version</name> > </property> > </activation> > <build> > <plugins> > <plugin> > > <groupId>org.maven.ide.eclipse</groupId> > > <artifactId>lifecycle-mapping</artifactId> > <configuration> > > <mappingId>customizable</mappingId> > <configurators> > <configurator > id="org.maven.ide.eclipse.configuration.wtp.configurator" /> > </configurators> > <mojoExecutions> > > <mojoExecution>org.apache.maven.plugins:maven-resources-plugin::</mojoExecution> > </mojoExecutions> > </configuration> > </plugin> > </plugins> > </build> > </profile> > </profiles> > > Mike > > On Thu, Apr 14, 2011 at 10:45 AM, Fred Bricon <[email protected]> wrote: >> Hi, >> >> I've just added a modification which I believe might fix most NPEs people >> get during project import or configuration. ([1], [2], [3], [4]) It will >> also help removing test classes and resources that sometimes get deployed >> with your app [5]. >> >> So if you can, I strongly encourage you to test the latest CI build >> available under >> https://repository.sonatype.org/content/sites/forge-sites/m2eclipse-wtp/0.12.0/N/<latest_directory> >> and give me your feedback, I can't reproduce said bugs >> >> 0.12.0 is closing in :-) >> >> regards, >> >> Fred Bricon >> >> [1] https://issues.sonatype.org/browse/MECLIPSEWTP-3 >> [2] https://issues.sonatype.org/browse/MECLIPSEWTP-14 >> [3] https://issues.sonatype.org/browse/MECLIPSEWTP-41 >> [4] https://issues.sonatype.org/browse/MECLIPSEWTP-42 >> [5] https://issues.sonatype.org/browse/MECLIPSEWTP-7 >> >> -- >> "Have you tried turning it off and on again" - The IT Crowd >> >> _______________________________________________ >> m2e-dev mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/m2e-dev >> >> > _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
