Both are still early and I'm sure there will be support for these things, especially if they are filed as requests. I'm not saying that the current eclipse plugin isn't still useful now, I just personally see it being less popular over time. I know that I used to live or die by the m-e-p, but once the new m2e came out, I haven't used it once.
Either way, I might suggest embarking on this rewrite on a separate branch from the current m-e-p code so that you can still maintain the old one for a bit. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of nicolas de loof Sent: Wednesday, April 23, 2008 10:46 AM To: Maven Developers List Subject: Re: [proposal] eclipse plugin extensibility Because those plugins doesn't support custom setup : I'm using the sysdeo-tomcat plugin to setup tomcat plugin for eclipse. It makes my life simplier but is ignored by q4e / m2eclipse. And AFAIK neither m2eclipse nor q4e support to read the maven checkstyle(*) configuration to setup checkstyle(*) plugin, (*) : replace with your favorite plugin. Nico. 2008/4/23, Benjamin Bentmann <[EMAIL PROTECTED]>: > > Now that there are two real eclipse plugins for maven, I have to wonder > > how much use this plugin will continue to get and if it's worth such a > > major overhaul? > > > > A possible reason to use the maven-eclipse-plugin: > It's not as invasive as Q4E or M2Eclipse. You can invoke it once on your > own > discretion and it won't invoke "mvn generate-resources" during every > Eclipse > startup, saving one from waiting. > > > Benjamin > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
