Plugin execution not covered by lifecycle configuration - Githubissues

adobe / aem-eclipse-developer-tools

The Eclipse plugin that brings you the full connection to the Adobe Experience Manager, with auto-sync and project creation wizard.

Apache License 2.0

35 stars 23 forks source link

Plugin execution not covered by lifecycle configuration #5

Closed gabrielwalt closed 10 years ago

gabrielwalt commented 10 years ago

Description

When creating a new AEM project, there are multiple (17) Eclipse errors on the various pom.xml, all starting with "Plugin execution not covered by lifecycle configuration".

Environment

Java 1.8.0_20
Eclipse Luna 4.4.0
Maven 3.2.1
Sling IDE Tools 1.0.2
AEM IDE Tools: UI-Extensions 1.0.0
Steps to reproduce
Create a new AEM Sample Multi-Module Project
Achtetype: com.adobe.granite.archetypes: sample-project-archetype: 7
Keep default settings (name: Example, group: org.myorg, artefact: example)
Detailed error listing

Description	Resource	Path	Location	Type
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-enforcer-plugin:1.0.1:enforce (execution: enforce-maven, phase: validate)	pom.xml	/example.core	line 18	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-resources-plugin:2.5:resources (execution: default-resources, phase: process-resources)	pom.xml	/example.core	line 18	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-resources-plugin:2.5:testResources (execution: default-testResources, phase: process-test-resources)	pom.xml	/example.core	line 18	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-enforcer-plugin:1.0.1:enforce (execution: enforce-maven, phase: validate)	pom.xml	/example.it.launcher	line 19	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-resources-plugin:2.5:resources (execution: default-resources, phase: process-resources)	pom.xml	/example.it.launcher	line 19	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-resources-plugin:2.5:testResources (execution: default-testResources, phase: process-test-resources)	pom.xml	/example.it.launcher	line 19	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-enforcer-plugin:1.0.1:enforce (execution: enforce-maven, phase: validate)	pom.xml	/example.it.tests	line 22	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-enforcer-plugin:1.0.1:enforce (execution: enforce-maven, phase: validate)	pom.xml	/example.ui.apps	line 22	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-enforcer-plugin:1.0.1:enforce (execution: enforce-maven, phase: validate)	pom.xml	/example.ui.content	line 22	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-resources-plugin:2.5:resources (execution: default-resources, phase: process-resources)	pom.xml	/example.it.tests	line 22	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-resources-plugin:2.5:testResources (execution: default-testResources, phase: process-test-resources)	pom.xml	/example.it.tests	line 22	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-resources-plugin:2.5:resources (execution: default-resources, phase: process-resources)	pom.xml	/example.ui.apps	line 82	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-resources-plugin:2.5:resources (execution: default-resources, phase: process-resources)	pom.xml	/example.ui.content	line 82	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-resources-plugin:2.5:testResources (execution: default-testResources, phase: process-test-resources)	pom.xml	/example.ui.apps	line 82	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-resources-plugin:2.5:testResources (execution: default-testResources, phase: process-test-resources)	pom.xml	/example.ui.content	line 82	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-resources-plugin:2.5:copy-resources (execution: copy-metainf-vault-resources, phase: generate-resources)	pom.xml	/example.ui.apps	line 90	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-resources-plugin:2.5:copy-resources (execution: copy-metainf-vault-resources, phase: generate-resources)	pom.xml	/example.ui.content	line 90	Maven Project Build Lifecycle Mapping Problem

gabrielwalt commented 10 years ago

This issue happened because Eclipse Standard was used instead of Eclipse for Java EE. Using the Java EE version doesn't cause these lifecycle problems when creating a new AEM project.