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 <victor.n...@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: cib...@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/

Reply via email to