camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gregor Zurowski (JIRA)" <>
Subject [jira] [Closed] (CAMEL-6668) Add m2e support to camel pom configuration
Date Thu, 24 Apr 2014 01:46:18 GMT


Gregor Zurowski closed CAMEL-6668.

       Resolution: Duplicate
    Fix Version/s: 2.14.0
         Assignee: Gregor Zurowski

The requested functionality has been implemented with CAMEL-7346.

> Add m2e support to camel pom configuration
> ------------------------------------------
>                 Key: CAMEL-6668
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>          Components: build system
>    Affects Versions: 2.11.1
>            Reporter: Tom Ellis
>            Assignee: Gregor Zurowski
>            Priority: Minor
>              Labels: build, m2e, maven, patch
>             Fix For: 2.14.0
>         Attachments: m2e.patch
> The m2e eclipse plugin requires additional lifecycle mapping configuration for maven
plugins that do not contribute this info.
> I've made a first attempt to add these mappings for the maven plugins used by the camel
projects in the attached patch, where I've mapped out the plugins that require mapping to
all execute.
> Importing projects using the m2e 'Import -> Existing Maven Projects' will work, although
perhaps not straight off the bat. I found it best to import all the camel projects into a
working set, cancel the immediate attempt to build after import, then right click on the working
set and go Maven -> Update Project and let it build from there. If a couple of projects
such as camel-jibx still give errors, another Update Project on the individual project should
fix. Obviously it would be nicer if these directly after import, but I believe there is a
build ordering issue. I am unsure of what plugins could actually be set to ignore and that
wouldn't affect building/testing within eclipse so have just set all to execute - I'll let
those who know the build setup better decide if some can be ignored.
> A couple of requirements:
> For the camel-groovy project, the GroovyEclipse plugin and GroovyEclipse M2E connector
must be obtained from the marketplace.
> For the camel-scala project, the Scala IDE plugin and m2eclipse-scala connector must
be obtained as described on
> I was running Eclipse 4.3 Kepler on jdk 7_45 - I found that the cxf codegen maven plugin
would use JAX-WS 2.2 when compiling soap wsdls, so I had to add the jaxws21 frontend to ensure
these were created with 2.1. This may need to be changed when Camel starts getting built with
source/target 1.7?

This message was sent by Atlassian JIRA

View raw message