[
http://jira.codehaus.org/browse/MCHECKSTYLE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87797
]
Jan Palmquist commented on MCHECKSTYLE-70:
------------------------------------------
Many other plugins have the same limitation, and after looking at the
pmd-plugin, I found a way to solve my issue temporarily simply letting
<sourceDirectory> point to the parent project src/main instead of pointing to
src/main/java.
This, however, breaks the xref-links since the src/main is not the actual
source folder.
In my case, I have an additional source folder src/main/java-generated holding
generated source code which I wan't to be separated from the hand written
source in order to delete it whenever I run mvn clean...
> Support for multiple source folders
> -----------------------------------
>
> Key: MCHECKSTYLE-70
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-70
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Improvement
> Affects Versions: 2.1
> Reporter: Jan Palmquist
> Priority: Minor
>
> It would be great if this plugin would support multiple source folders added
> by http://mojo.codehaus.org/build-helper-maven-plugin/ (or similar), and by
> default inspect sources from these folders instead of just
> ${project.build.sourceDirectory}. Correspondingly with respect to test
> sources if those are configured to be included.
> There are other plugins available solving this problem (somehow), eg:
> * http://mojo.codehaus.org/jdepend-maven-plugin/
> * http://mojo.codehaus.org/findbugs-maven-plugin/
> Maybe they can give some inspiration for how to make this possible?
--
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
