You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Victor NOËL <vi...@linagora.com> on 2015/05/12 14:42:42 UTC
Making the Camel Maven plugins Eclipse compatible
Hi,
There is a set of recommendations to make a maven plugin eclipse-compatible:
http://eclipse.org/m2e/documentation/m2e-making-maven-plugins-compat.html
In particular, the use of BuildContext is very important because it
prevents mismatch between the state produced by the execution of a maven
plugin and the state seen by eclipse.
Without eclipse, it has no performance overhead.
For example, I am using camel-package-maven-plugin for my camel
component and in Eclipse, the generation of code triggers a rebuild
which triggers generation of code and this indefinitely.
Using the BuildContext would prevent such situation normally.
It would be nice if it was used in the camel maven plugins :)
Thanks!
Re: Making the Camel Maven plugins Eclipse compatible
Posted by Victor NOËL <vi...@linagora.com>.
FYI the PR is there: https://github.com/apache/camel/pull/518
Le 18/05/2015 12:30, Victor NOËL a écrit :
> Hi,
>
> So I have been working on a PR for that.
>
> Can you clarify something for me?
>
> Only camel-maven-plugin, camel-package-maven-plugin and
> guice-maven-plugin are meant to be used by non camel team developers?
> And the goals generate-and-attach-archetype-catalog,
> generate-eips-list and prepare-catalog (from
> camel-package-maven-plugin) are also meant to be only used internally
> by the camel team?
>
> As for camel-api-component-maven-plugin and
> camel-eip-documentation-enricher-maven-plugin, they are used
> internally by the Camel team?
>
> Is that right or are things different?
>
> Thank you
>
> Victor
>
> Le 12/05/2015 20:30, Claus Ibsen a écrit :
>> Hi
>>
>> We love contributions
>> http://camel.apache.org/contributing.html
>>
>> So you or any Eclipse users is welcome to dive in to see what changes
>> is needed in the pom.xml and submit a patch / PR.
>>
>> On Tue, May 12, 2015 at 2:42 PM, Victor NOËL
>> <vi...@linagora.com> wrote:
>>> Hi,
>>>
>>> There is a set of recommendations to make a maven plugin
>>> eclipse-compatible:
>>> http://eclipse.org/m2e/documentation/m2e-making-maven-plugins-compat.html
>>>
>>>
>>> In particular, the use of BuildContext is very important because it
>>> prevents
>>> mismatch between the state produced by the execution of a maven
>>> plugin and
>>> the state seen by eclipse.
>>> Without eclipse, it has no performance overhead.
>>>
>>> For example, I am using camel-package-maven-plugin for my camel
>>> component
>>> and in Eclipse, the generation of code triggers a rebuild which
>>> triggers
>>> generation of code and this indefinitely.
>>>
>>> Using the BuildContext would prevent such situation normally.
>>>
>>> It would be nice if it was used in the camel maven plugins :)
>>>
>>> Thanks!
>>
>>
>
Re: Making the Camel Maven plugins Eclipse compatible
Posted by Claus Ibsen <cl...@gmail.com>.
On Mon, May 18, 2015 at 12:30 PM, Victor NOËL <vi...@linagora.com> wrote:
> Hi,
>
> So I have been working on a PR for that.
>
> Can you clarify something for me?
>
> Only camel-maven-plugin, camel-package-maven-plugin and guice-maven-plugin
> are meant to be used by non camel team developers?
Yes they are for end users. Though camel-package-maven-plugin is a mix.
> And the goals generate-and-attach-archetype-catalog, generate-eips-list and
> prepare-catalog (from camel-package-maven-plugin) are also meant to be only
> used internally by the camel team?
>
Yeah all that is internal.
> As for camel-api-component-maven-plugin and
> camel-eip-documentation-enricher-maven-plugin, they are used internally by
> the Camel team?
>
No they are also for end users when they create custom components that
are api based, and they want to leverage the component api support.
This allows to build components against apis such as social like
facebook, linkedin, salesforce, etc that has massive rest apis. These
plugins is there fore some source code generation.
> Is that right or are things different?
>
> Thank you
>
> Victor
>
>
> Le 12/05/2015 20:30, Claus Ibsen a écrit :
>>
>> Hi
>>
>> We love contributions
>> http://camel.apache.org/contributing.html
>>
>> So you or any Eclipse users is welcome to dive in to see what changes
>> is needed in the pom.xml and submit a patch / PR.
>>
>> On Tue, May 12, 2015 at 2:42 PM, Victor NOËL <vi...@linagora.com>
>> wrote:
>>>
>>> Hi,
>>>
>>> There is a set of recommendations to make a maven plugin
>>> eclipse-compatible:
>>> http://eclipse.org/m2e/documentation/m2e-making-maven-plugins-compat.html
>>>
>>> In particular, the use of BuildContext is very important because it
>>> prevents
>>> mismatch between the state produced by the execution of a maven plugin
>>> and
>>> the state seen by eclipse.
>>> Without eclipse, it has no performance overhead.
>>>
>>> For example, I am using camel-package-maven-plugin for my camel component
>>> and in Eclipse, the generation of code triggers a rebuild which triggers
>>> generation of code and this indefinitely.
>>>
>>> Using the BuildContext would prevent such situation normally.
>>>
>>> It would be nice if it was used in the camel maven plugins :)
>>>
>>> Thanks!
>>
>>
>>
>
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/
Re: Making the Camel Maven plugins Eclipse compatible
Posted by Victor NOËL <vi...@linagora.com>.
Hi,
So I have been working on a PR for that.
Can you clarify something for me?
Only camel-maven-plugin, camel-package-maven-plugin and
guice-maven-plugin are meant to be used by non camel team developers?
And the goals generate-and-attach-archetype-catalog, generate-eips-list
and prepare-catalog (from camel-package-maven-plugin) are also meant to
be only used internally by the camel team?
As for camel-api-component-maven-plugin and
camel-eip-documentation-enricher-maven-plugin, they are used internally
by the Camel team?
Is that right or are things different?
Thank you
Victor
Le 12/05/2015 20:30, Claus Ibsen a écrit :
> Hi
>
> We love contributions
> http://camel.apache.org/contributing.html
>
> So you or any Eclipse users is welcome to dive in to see what changes
> is needed in the pom.xml and submit a patch / PR.
>
> On Tue, May 12, 2015 at 2:42 PM, Victor NOËL <vi...@linagora.com> wrote:
>> Hi,
>>
>> There is a set of recommendations to make a maven plugin eclipse-compatible:
>> http://eclipse.org/m2e/documentation/m2e-making-maven-plugins-compat.html
>>
>> In particular, the use of BuildContext is very important because it prevents
>> mismatch between the state produced by the execution of a maven plugin and
>> the state seen by eclipse.
>> Without eclipse, it has no performance overhead.
>>
>> For example, I am using camel-package-maven-plugin for my camel component
>> and in Eclipse, the generation of code triggers a rebuild which triggers
>> generation of code and this indefinitely.
>>
>> Using the BuildContext would prevent such situation normally.
>>
>> It would be nice if it was used in the camel maven plugins :)
>>
>> Thanks!
>
>
Re: Making the Camel Maven plugins Eclipse compatible
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
We love contributions
http://camel.apache.org/contributing.html
So you or any Eclipse users is welcome to dive in to see what changes
is needed in the pom.xml and submit a patch / PR.
On Tue, May 12, 2015 at 2:42 PM, Victor NOËL <vi...@linagora.com> wrote:
> Hi,
>
> There is a set of recommendations to make a maven plugin eclipse-compatible:
> http://eclipse.org/m2e/documentation/m2e-making-maven-plugins-compat.html
>
> In particular, the use of BuildContext is very important because it prevents
> mismatch between the state produced by the execution of a maven plugin and
> the state seen by eclipse.
> Without eclipse, it has no performance overhead.
>
> For example, I am using camel-package-maven-plugin for my camel component
> and in Eclipse, the generation of code triggers a rebuild which triggers
> generation of code and this indefinitely.
>
> Using the BuildContext would prevent such situation normally.
>
> It would be nice if it was used in the camel maven plugins :)
>
> Thanks!
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/
Re: Making the Camel Maven plugins Eclipse compatible
Posted by Victor NOËL <vi...@linagora.com>.
FYI Preben, the pull request I made was merged and will be released with
version 2.16 I guess :)
Le 12/05/2015 19:52, Preben.Asmussen a écrit :
> +1
>
> Best,
> Preben
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Making-the-Camel-Maven-plugins-Eclipse-compatible-tp5767009p5767020.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Making the Camel Maven plugins Eclipse compatible
Posted by "Preben.Asmussen" <pr...@dr.dk>.
+1
Best,
Preben
--
View this message in context: http://camel.465427.n5.nabble.com/Making-the-Camel-Maven-plugins-Eclipse-compatible-tp5767009p5767020.html
Sent from the Camel - Users mailing list archive at Nabble.com.