Re: [m2e-dev] Configurator priorities

[Olivier NOUGUIER <olivier.nouguier@xxxxxxxxx>]

Thank you Igor.

So It's common to provide more than one configurator (GWT) for supporting a mojo.

In my situation (GWT) I have some goals that I want to support:

 - compile (phase package)

 - i18n (phase process-resources)

 - generateAsync

"i18n" and "generateAsync" run early as they are generating some sources (phase process-resources)

"compile" need to runs after the JDT configuration to be able to add GWTNature (phase package).

So to support those goal I've had to provide 2 configurators: one for "compile" and one for "i18n" and "generateAsync". 

Could we generalize by saying that goals support of a given mojo have to/can be gathered in same configurator on the basis of their running phase ?

Regards,

Olivier

On Tue, Jul 19, 2011 at 7:17 AM, Igor Fedorenko <igor@xxxxxxxxxxxxxx> wrote:

Configurators are invoked in the order of their corresponding maven
plugin executions.

--
Regards,
Igor

On 11-07-19 1:24 AM, Olivier NOUGUIER wrote:

hi,
 I have the feeling that configurators providing build participant are
run before the other, is it the reality ?

--
"Computers are useless. They can only give you answers."
- Pablo Picasso -

_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev

_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev

--
"Computers are useless. They can only give you answers."
- Pablo Picasso -