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
<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!
