Re: [m2e-dev] Plugin execution not covered by lifecycle configuration

[Igor Fedorenko <igor@xxxxxxxxxxxxxx>]

m2e allows pluginExecutions mapping specific to a packaging type, i.e.
defined under <lifecycleMapping/> element with packagingType=avk of your
lifecycle-mapping-metadata.xml (for example, see how m2e-wtp does this
in [1]).

Don't map maven-jar-plugin globally, as this will enable your mapping
for all projects, something you don't want to do most likely.

[1] 
https://github.com/sonatype/m2eclipse-wtp/blob/master/org.maven.ide.eclipse.wtp/lifecycle-mapping-metadata.xml

--
Regards,
Igor

On 11-05-24 05:32 AM, Ricardo Gladwell wrote:
> What would be the impact of mapping the
> org.apache.maven.plugins:maven-jar-plugin:default-jar to my m2eclipse
> extension in my lifecycle-mapping-metadata.xml?
>
> --
> Ricardo Gladwell<ricardo.gladwell@xxxxxxxxx>
> http://www.google.com/profiles/ricardo.gladwell
> Twitter: @rgladwell - MSN: axonrg@xxxxxxxxx
>
>
>
> On 20 May 2011 17:58, Igor Fedorenko<igor@xxxxxxxxxxxxxx>  wrote:
> > It most likely comes from packaging=avk. You use "mvn
> > help:effective-pom" to see complete pom.xml with all inherited plugins.
> >
> > lifecycle-mapping-metadata.xml does not add/remove plugin executions to
> > project, it only tells m2e what to do with executions that are bound in
> > pom.xml or inherited from parent pom or implied by packaging type.
> >
> > --
> > Regards,
> > Igor
> >
> > On 11-05-20 12:48 PM, Ricardo Gladwell wrote:
> > > Hi Igor
> > >
> > > Thanks again for your help.
> > >
> > > Checking my test project and I can't see the maven-jar-plugin:jar
> > > bound to process-classes
> > > build lifecycle phase (see attached).
> > >
> > > I noticed that maven-jar-plugin was bound in my
> > > lifecycle-mapping-metadata.xml pluginExecutionFilter. I have removed
> > > this, but am still getting a similar error in my unit tests (see
> > > attached stacktrace.log).
> > >
> > > Please advise, TIA...
> > >
> > > --
> > > Ricardo Gladwell<ricardo.gladwell@xxxxxxxxx>
> > > http://www.google.com/profiles/ricardo.gladwell
> > > Twitter: @rgladwell - MSN: axonrg@xxxxxxxxx
> > >
> > >
> > >
> > > On 20 May 2011 16:43, Igor Fedorenko<igor@xxxxxxxxxxxxxx>    wrote:
> > > > Your test project has maven-jar-plugin:jar bound to process-classes
> > > > build lifecycle phase and m2e does not have explicit mapping for this
> > > > plugging.
> > > >
> > > > Note that normally, maven-jar-plugin is bound to package phase iirc,
> > > > which is ignored by m2e by default (see [1]). What do you use jar:jar
> > > > for?
> > > > Do you actually need it bound to process-classes?
> > > >
> > > > [1]
> > > >
> > > > https://docs.sonatype.org/display/M2ECLIPSE/Project+build+lifecycle+mapping
> > > >
> > > > --
> > > > Regards,
> > > > Igor
> > > >
> > > > On 11-05-20 10:42 AM, Ricardo Gladwell wrote:
> > > > > Hi Guys
> > > > >
> > > > > Re-writing my AbstractMavenProjectTestCase based PDE unit tests for my
> > > > > m2eclipse-android-integration using the LATEST build of m2e 0.13.0.
> > > > > However, my tests are failing on a call to assertNoErrors (see
> > > > > attached stack trace) with the following error message:
> > > > >
> > > > > Unexpected error markers
> > > > > Type=org.eclipse.m2e.core.maven2Problem.lifecycleMapping:Message=Plugin
> > > > > execution not covered by lifecycle configuration:
> > > > > org.apache.maven.plugins:maven-jar-plugin:2.3.1:jar (execution:
> > > > > default-jar, phase: process-classes):LineNumber=22,
> > > > > Type=org.eclipse.m2e.core.maven2Problem.lifecycleMapping:Message=Project
> > > > > configurator "org.sonatype.m2e.mavenarchiver.pomProperties" is not
> > > > > available. To enable full functionality, install the project
> > > > > configurator and run Maven->Update Project
> > > > > Configuration.:LineNumber=22 expected:<0>      but was:<2>
> > > > >
> > > > > Any ideas why this might be occuring? Am I doing something wrong?
> > > > >
> > > > > TIA...
> > > > >
> > > > > --
> > > > > Ricardo Gladwell<ricardo.gladwell@xxxxxxxxx>
> > > > > http://www.google.com/profiles/ricardo.gladwell
> > > > > Twitter: @rgladwell - MSN: axonrg@xxxxxxxxx