[
https://issues.apache.org/jira/browse/CAMEL-7326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregor Zurowski resolved CAMEL-7326.
------------------------------------
Resolution: Fixed
Closing issue after updating the m2e section on the "Building" page
(http://camel.apache.org/building.html). Please feel free to reopen this
ticket, if more details need to be added to the documentation.
> Improve Eclipse development with m2e Maven integration
> ------------------------------------------------------
>
> Key: CAMEL-7326
> URL: https://issues.apache.org/jira/browse/CAMEL-7326
> Project: Camel
> Issue Type: Improvement
> Reporter: Gregor Zurowski
> Assignee: Gregor Zurowski
> Priority: Minor
> Fix For: 2.14.0
>
> Attachments: Eclipse m2e Import Errors.jpg, Eclipse m2e Import
> Without Errors After Applying Patch.jpg, Eclipse m2e Lifecycle Errors after
> Import.jpg
>
>
> Importing the Camel code base using Eclipse and the m2e plugin currently
> results in numerous errors due to missing lifecycle mappings for some Maven
> plugins. The following errors occur during the import process:
> "Plugin execution not covered by lifecycle configuration"
> To improve and simplify development using Eclipse, missing lifecycle mappings
> need to be manually provided in pom.xml files for all plugins that do not
> provide such information (see
> http://wiki.eclipse.org/M2E_plugin_execution_not_covered). As a result, it
> should be possible to import all Camel projects using m2e (i.e. Import ->
> Existing Maven Projects) without the need to generate Eclipse settings
> (.classpath/.project/.settings) using the maven-eclipse-plugin.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
