Re: [m2e-dev] Way to trigger eclipse configurator

[Matthew Piggott <mpiggott@xxxxxxxxxxxx>]

I don't have an answer to your question, but you should avoid using the org.eclipse namespace unless the project is hosted at Ecipse ;)

Matthew

On 14 February 2012 08:50, Olivier NOUGUIER <olivier.nouguier@xxxxxxxxx> wrote:

Hi all,
  I'm replying to myself with a solution to my problem and another two questions.

 What I've done [1]:

•   remove the lifecycle mapping to maven-eclipse-plugin:eclipse
  
•   declare a secondary (to org.eclipse.m2e.jdt.javaConfigurator) configurator to the maven-complile-plugin:compile goal
•   still using my mojo configuration but without associated goal.

Now the configurator is call anytime it encounter the maven-compiler-plugin:compile goal and does nothing if the maven-eclipse-plugin build plugins is not there.

Is acceptable?

Should I prefer use the pluginManagement as the maven-eclipse-plugin as no goal are associated?

[1] https://github.com/cheleb/m2e-settings/tree/nogoal

Thx,
Olivier

On Sat, Feb 11, 2012 at 6:21 PM, Olivier NOUGUIER <olivier.nouguier@xxxxxxxxx> wrote:

Hi all,
 
   I have built an eclipse configurator to tune the eclipse formatting settings [1].

   To trigger the configurator I'm using a fake Mojo&goal only to use its dependencies and configurations.
 
   Is there another solution, that could avoid this fake mojo and goal ?


[1] https://github.com/cheleb/m2e-settings

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

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