Camel › Camel Development

Using Eclipse (STS) for building Camel

Classic

List

Threaded

6 messages Options

magnuspalmer

Using Eclipse (STS) for building Camel

Dear all,

I am new to the dev-list and the reason for that is because I will from now
on not only use Camel but also try to contribute every now and then.
To gete started I created a JIRA ticket the other day for the
Bindy-component that I will now extend the current insufficient test-case
for tab separators and hopefully patch the bug as well.
In doing so I managed to set up my dev-environment so I can build the
trunk, but I would also like to be able to use m2e with Eclipse instead of
the mvn eclipse:eclipse
I couldn't find any information regarding that using Nabble. Problem is
that there are some "M2E plugin executions not covered" -
http://wiki.eclipse.org/M2E_plugin_execution_not_covered.

Just want a quick advice, should I try spend time on getting this to work,
or settle for the mvn eclipse:eclipse variant?
What are you others using for setup?

Kind regards, Magnus Palmér

Christian Schneider

Re: Using Eclipse (STS) for building Camel

The easiest way is to use the old version of m2e.
The new version by default supports non of the maven build plugins which
makes it really suck in my opinion.

I just checked their website and they removed the link to the archive.
So I guess that m2eclipse is now not usable for camel anymore.

Christian

Am 02.04.2012 11:57, schrieb Magnus Palmér:

> Dear all,
>
> I am new to the dev-list and the reason for that is because I will from now
> on not only use Camel but also try to contribute every now and then.
> To gete started I created a JIRA ticket the other day for the
> Bindy-component that I will now extend the current insufficient test-case
> for tab separators and hopefully patch the bug as well.
> In doing so I managed to set up my dev-environment so I can build the
> trunk, but I would also like to be able to use m2e with Eclipse instead of
> the mvn eclipse:eclipse
> I couldn't find any information regarding that using Nabble. Problem is
> that there are some "M2E plugin executions not covered" -
> http://wiki.eclipse.org/M2E_plugin_execution_not_covered.
>
> Just want a quick advice, should I try spend time on getting this to work,
> or settle for the mvn eclipse:eclipse variant?
> What are you others using for setup?
>
> Kind regards, Magnus Palmér
>

--

Christian Schneider
http://www.liquid-reality.de

Open Source Architect
Talend Application Integration Division http://www.talend.com

Claus Ibsen-2

Re: Using Eclipse (STS) for building Camel

In reply to this post by magnuspalmer

Eclipse 3.7 has built-in maven support now.
So you can just import -> maven -> existing maven project

2012/4/2 Magnus Palmér <[hidden email]>:

--
Claus Ibsen
-----------------
CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
FuseSource
Email: [hidden email]
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/

magnuspalmer

Re: Using Eclipse (STS) for building Camel

Well, the built in Maven support is "M2E - Maven Integration for Eclipse"
(formerly the m2eclipse plugin).
That is what is not working out-of-the-box due to "M2E plugin executions
not covered".
Since I can't get started with all things at once, I'll settle with the mvn
eclipse:eclipse for now.

Den 2 april 2012 13:10 skrev Claus Ibsen <[hidden email]>:

> Eclipse 3.7 has built-in maven support now.
> So you can just import -> maven -> existing maven project
>
>
> 2012/4/2 Magnus Palmér <[hidden email]>:
> > Dear all,
> >
> > I am new to the dev-list and the reason for that is because I will from
> now
> > on not only use Camel but also try to contribute every now and then.
> > To gete started I created a JIRA ticket the other day for the
> > Bindy-component that I will now extend the current insufficient test-case
> > for tab separators and hopefully patch the bug as well.
> > In doing so I managed to set up my dev-environment so I can build the
> > trunk, but I would also like to be able to use m2e with Eclipse instead
> of
> > the mvn eclipse:eclipse
> > I couldn't find any information regarding that using Nabble. Problem is
> > that there are some "M2E plugin executions not covered" -
> > http://wiki.eclipse.org/M2E_plugin_execution_not_covered.
> >
> > Just want a quick advice, should I try spend time on getting this to
> work,
> > or settle for the mvn eclipse:eclipse variant?
> > What are you others using for setup?
> >
> > Kind regards, Magnus Palmér
>
>
>
> --
> Claus Ibsen
> -----------------
> CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
> FuseSource
> Email: [hidden email]
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
>

Christian Schneider

Re: Using Eclipse (STS) for building Camel

Try this version:
http://m2eclipse.sonatype.org/sites/m2e/0.12.1.20110112-1712/

I use it and it works with camel.

Christian

Am 02.04.2012 13:19, schrieb Magnus Palmér:

> Well, the built in Maven support is "M2E - Maven Integration for Eclipse"
> (formerly the m2eclipse plugin).
> That is what is not working out-of-the-box due to "M2E plugin executions
> not covered".
> Since I can't get started with all things at once, I'll settle with the mvn
> eclipse:eclipse for now.
>
>
> Den 2 april 2012 13:10 skrev Claus Ibsen<[hidden email]>:
>
>> Eclipse 3.7 has built-in maven support now.
>> So you can just import -> maven -> existing maven project
>>
>>
>> 2012/4/2 Magnus Palmér<[hidden email]>:
>>> Dear all,
>>>
>>> I am new to the dev-list and the reason for that is because I will from
>> now
>>> on not only use Camel but also try to contribute every now and then.
>>> To gete started I created a JIRA ticket the other day for the
>>> Bindy-component that I will now extend the current insufficient test-case
>>> for tab separators and hopefully patch the bug as well.
>>> In doing so I managed to set up my dev-environment so I can build the
>>> trunk, but I would also like to be able to use m2e with Eclipse instead
>> of
>>> the mvn eclipse:eclipse
>>> I couldn't find any information regarding that using Nabble. Problem is
>>> that there are some "M2E plugin executions not covered" -
>>> http://wiki.eclipse.org/M2E_plugin_execution_not_covered.
>>>
>>> Just want a quick advice, should I try spend time on getting this to
>> work,
>>> or settle for the mvn eclipse:eclipse variant?
>>> What are you others using for setup?
>>>
>>> Kind regards, Magnus Palmér
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
>> FuseSource
>> Email: [hidden email]
>> Web: http://fusesource.com
>> Twitter: davsclaus, fusenews
>> Blog: http://davsclaus.blogspot.com/
>> Author of Camel in Action: http://www.manning.com/ibsen/
>>

--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
Talend Application Integration Division http://www.talend.com

hadrian

Re: Using Eclipse (STS) for building Camel

In reply to this post by magnuspalmer

The M2E plugin is also very slow, I am not happy with it for larger
projects, but I use it with small projects. Here's what I do for Camel
builds:

mvn clean install -Dfastinstall
mvn -Psetup.eclipse

in Eclipse:
File -> Import... -> General/Existing Projects into Workspace

I hope this helps,
Hadrian

On 04/02/2012 07:19 AM, Magnus Palmér wrote:

> Well, the built in Maven support is "M2E - Maven Integration for Eclipse"
> (formerly the m2eclipse plugin).
> That is what is not working out-of-the-box due to "M2E plugin executions
> not covered".
> Since I can't get started with all things at once, I'll settle with the mvn
> eclipse:eclipse for now.
>
>
> Den 2 april 2012 13:10 skrev Claus Ibsen<[hidden email]>:
>
>> Eclipse 3.7 has built-in maven support now.
>> So you can just import -> maven -> existing maven project
>>
>>
>> 2012/4/2 Magnus Palmér<[hidden email]>:
>>> Dear all,
>>>
>>> I am new to the dev-list and the reason for that is because I will from
>> now
>>> on not only use Camel but also try to contribute every now and then.
>>> To gete started I created a JIRA ticket the other day for the
>>> Bindy-component that I will now extend the current insufficient test-case
>>> for tab separators and hopefully patch the bug as well.
>>> In doing so I managed to set up my dev-environment so I can build the
>>> trunk, but I would also like to be able to use m2e with Eclipse instead
>> of
>>> the mvn eclipse:eclipse
>>> I couldn't find any information regarding that using Nabble. Problem is
>>> that there are some "M2E plugin executions not covered" -
>>> http://wiki.eclipse.org/M2E_plugin_execution_not_covered.
>>>
>>> Just want a quick advice, should I try spend time on getting this to
>> work,
>>> or settle for the mvn eclipse:eclipse variant?
>>> What are you others using for setup?
>>>
>>> Kind regards, Magnus Palmér
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
>> FuseSource
>> Email: [hidden email]
>> Web: http://fusesource.com
>> Twitter: davsclaus, fusenews
>> Blog: http://davsclaus.blogspot.com/
>> Author of Camel in Action: http://www.manning.com/ibsen/
>>
>

--
Hadrian Zbarcea
Principal Software Architect
Talend, Inc
http://coders.talend.com/
http://camelbot.blogspot.com/