camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-7326) Improve Eclipse development with m2e Maven integration
Date Wed, 26 Mar 2014 03:11:15 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-7326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13947499#comment-13947499
] 

ASF GitHub Bot commented on CAMEL-7326:
---------------------------------------

GitHub user gzurowski opened a pull request:

    https://github.com/apache/camel/pull/118

    CAMEL-7326: Add Eclipse m2e lifecycle mappings

    Signed-off-by: Gregor Zurowski <gregor@zurowski.org>

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gzurowski/camel CAMEL-7326

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/118.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #118
    
----
commit 713981a320bfb2006b50ca1c3e3a48c78662e5bd
Author: Gregor Zurowski <gregor@zurowski.org>
Date:   2014-03-26T03:05:15Z

    CAMEL-7326: Add Eclipse m2e lifecycle mappings
    
    Signed-off-by: Gregor Zurowski <gregor@zurowski.org>

----


> 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
>         Attachments: Eclipse m2e Import Errors.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)

Mime
View raw message