Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 345446

Summary:

No marketplace items are applicable for EAR projects (maven-ear-plugin:generate-application-xml)

Product:

z_Archived

Reporter:

Fred Bricon <fbricon>

Component:

m2e

Assignee:

Project Inbox <m2e.core-inbox>

Status:

CLOSED INVALID

QA Contact:

Severity:

normal

Priority:

CC:

igor, murray.waters

Version:

unspecified

Target Milestone:

---

Hardware:

OS:

Linux

Whiteboard:

Attachments:

Description	Flags
m2e marketplace doesn't find any applicable items for EAR packaging	none

Description Fred Bricon

2011-05-11 11:24:26 EDT

Created attachment 195376 [details]
m2e marketplace doesn't find any applicable items for EAR packaging

I just downloaded a JavaEE 3.7M7 distro, installed the latest m2e milestone (0.13.0.201104282116) and created an ear project (simple ear project, no archetype)
Upon creation, a marker appears : 
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-ear-plugin:2.4.2:generate-application-xml (execution: default-generate-application-xml, phase: generate-resources)

If I try to quick-fix it to discover new connectors, the m2e Marketplace window popups but displays "No marketplace items are applicable"

I expected the m2e discovery mechanism to associate m2e-wtp with ear projects.

The m2e-wtp lifecycle mapping metadata (https://github.com/sonatype/m2eclipse-wtp/blob/master/org.maven.ide.eclipse.wtp/lifecycle-mapping-metadata.xml#L73) declares the generate-application-xml should be ignored, for ear packaging.

If I select the Lifecycles checkbox, the m2e-wtp plugin is displayed though.

Comment 1 Fred Bricon

2011-05-11 11:27:53 EDT

> The m2e-wtp lifecycle mapping metadata
> (https://github.com/sonatype/m2eclipse-wtp/blob/master/org.maven.ide.eclipse.wtp/lifecycle-mapping-metadata.xml#L73)
> declares the generate-application-xml should be ignored, for ear packaging.

Scratch that : generate-application-xml is bound to a configurator. Damn, I don't even remember how my plugin works.

Comment 2 Igor Fedorenko

2011-05-11 21:00:10 EDT

I can confirm the problem still exists in the current master HEAD. The problem is limited to quick-fix. Import of existing ear projects correctly offers installation of m2e-wtp integration. Will look at this post Indigo.

Comment 3 Murray Waters

2011-09-07 01:16:24 EDT

Is there a workaround for this? can the error be safely ignored?

Comment 4 Fred Bricon

2011-11-07 20:28:52 EST

maven-ear-plugin:generate-application-xml is associated with the ear packaging.

I took a quick look at this and it appears MavenCatalogViewer is testing the maven-ear-plugin:generate-application-xml MojoExecutionKey against the lifecycleMappingMetadataSource.getPluginExecutions() but doesn't check if it's defined in the pluginExecutions from  lifecycleMappingMetadataSource.getLifecycleMappings(). 

DiscoveryWizardProposal doesn't send any informations regarding the packaging to MavenCatalogViewer, in case of "Plugin execution not covered".

Comment 5 Fred Bricon

2011-11-07 20:35:40 EST

Actually it seems the packaging types sent to MavenDiscovery.launchWizard are always an empty collection (https://github.com/eclipse/m2e-core/blob/master/org.eclipse.m2e.discovery/src/org/eclipse/m2e/internal/discovery/markers/DiscoveryWizardProposal.java#L54 and https://github.com/eclipse/m2e-core/blob/master/org.eclipse.m2e.discovery/src/org/eclipse/m2e/internal/discovery/markers/DiscoveryWizardProposal.java#L74).

Comment 6 Igor Fedorenko

2013-09-28 23:32:12 EDT

closing old/stale bugreports

Comment 7 Denis Roy

2021-04-19 13:22:57 EDT

Moved to https://github.com/eclipse-m2e/m2e-core/issues/