cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <dk...@apache.org>
Subject Re: M2Eclipse as an alternative to the maven-eclipse-plugin
Date Tue, 14 Dec 2010 15:28:44 GMT

I think if you go to "File -> Import -> General -> Preferences", you can 
import those preferences directly into the workspace.

Dan



On Tuesday 14 December 2010 9:16:32 am David Valeri wrote:
> I can confirm success over here too.  I imported the security module using
> M2Eclipse and the import completed successfully.
> 
> I noticed that you added eclipse.prefs to SVN.  I updated your instructions
> in the wiki last week since eclipse.prefs wasn't in source control.  If
> using it reduces the number of steps, please elaborate on what to do with
> it since I don't know how to "import" it.  There is an Eclipse preferences
> export format, but it is not a .prefs file.  Is one mechanism better than
> the other?
> 
> On Sat, Dec 11, 2010 at 8:57 PM, Benson Margulies 
<bimargulies@gmail.com>wrote:
> > OK, I think it works. If you set the profile m2eclipse, it will avoid
> > the custom-class PMD check, and you should get the same treatment we
> > get from the maven-eclipse-plugin.
> > 
> > 
> > On Sat, Dec 11, 2010 at 8:41 PM, Benson Margulies <bimargulies@gmail.com>
> > 
> > wrote:
> > > I see what the trick is here.
> > > 
> > > When running in eclipse, the existing scheme plays a trick to use set
> > > of PMD rules that omits the custom rule, for the very reason you ran
> > > into. Unfortunately for us, the auto-configuration tries to pick them
> > > right back up, but that does not fly.
> > > 
> > > So, the question is, how to derail this? One way is to define a
> > > profile that redirects the PMD rules in the eclipse case. I'll have a
> > > look.

-- 
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog

Mime
View raw message