[ http://jira.codehaus.org/browse/MPMD-36?page=comments#action_69247 ]
Sharmarke Aden commented on MPMD-36: ------------------------------------ In response to Mike Perham comments: Are you guys familiar with the assembly plugin (http://maven.apache.org/plugins/maven-assembly-plugin/introduction.html)? It provides an alternative way of package an application and as it stands you can't use the PMD plugin in conjunction with the assembly plugin. I believe this is an issue the PMD plugin needs to deal with. My application is packaged in fashion similar to the how Jetty is packaged (http://prdownloads.sourceforge.net/jetty/jetty-5.1.10.zip?download) . Look at their directory structure and try using war packaging to create that sort of directory structure. In response to Brett Porter comment: My patch also insures that the project has a source directory defined before proceeding. The patch basically allows the PMD continue if the follow condition is met: ((java || pom) && has source) > PMD Reports Not Generated for Projects Using POM Packaging > ----------------------------------------------------------- > > Key: MPMD-36 > URL: http://jira.codehaus.org/browse/MPMD-36 > Project: Maven 2.x Pmd Plugin > Type: Bug > Versions: 2.0 > Environment: WinXP SP2, Pentium 4, Cygwin, Maven 2.0.4 > Reporter: Sharmarke Aden > Assignee: Mike Perham > Attachments: modulePOM.xml, parentPOM.xml, pmd-plugin_MPMD36.patch > > > My project uses the assembly plugin and thus uses pom based packaging: > <packaging>jar</packaging> > It seems that the PMD plugin only creates reports for projects utilizing > archive based packaging such as jar and war but not for projects using pom > based packaging. -- 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
