[ http://jira.codehaus.org/browse/MPMD-39?page=comments#action_79400 ] Eric Bernstein commented on MPMD-39: ------------------------------------
I haven't spent much time looking into this because the solution I came up with seemed kinda hacky and I wasn't sure anyone would want it if I did upload a patch. I was thinking something like having the pmd plugin traverse the build plugins (sort of how it detects the jxr-plugin now) and look for the configuration of the compiler plugin. This may be a bit of a hack from everyone's perspective, but if anyone thinks it might stand of chance of making it into the codebase, I'll be happy to take a go at implementing it. I would certainly understand if this seems a bit much of a hack for people's tastes though. It does imply that the pmd plugin understands how the compiler plugin is configured. > Target JDK should default to configuration of the compiler plugin > ----------------------------------------------------------------- > > Key: MPMD-39 > URL: http://jira.codehaus.org/browse/MPMD-39 > Project: Maven 2.x Pmd Plugin > Issue Type: Improvement > Reporter: Eric Bernstein > > It seems unnecessary to configure the target jdk twice; once for the > compiler, and once for pmd. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
