If you tell m2eclipse to import the projects with the m2eclipse profile enabled, then it switched to a different PMD ruleset that doesn't have the custom rule.
That said, I do have to wonder if we really need the custom rule anymore. It's just to trap calls to "new String(byte[])" which has issues due to the machine specific encoding. I just did some checking and that check is no longer working outside of eclipse either. Might as well just get rid of it. Dan On Sep 9, 2013, at 10:03 AM, Christian Schneider <[email protected]> wrote: > I am working on CXF using m2eclipse. > > When I import projects using m2eclipse or update the maven project I always > get an error that contains: > PMD UnsafeStringConstructorRule > > So it seems m2eclipse configures pmd but can not find the custom rule. > > I was able to get it running by removing this line in the parent pom. > <ruleset>${cxf.resources.base.path}cxf-pmd-custom.xml</ruleset> > > This line seems to add the problematic rule. > > Can this be fixed in a better way? > Do we really need these PMD checks in eclipse? > > Christian > > > -- > Christian Schneider > http://www.liquid-reality.de > > Open Source Architect > http://www.talend.com > -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
