maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Lundberg (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MCHECKSTYLE-64) Allow inclusion of javadoc source path in check
Date Sun, 03 Feb 2008 15:23:58 GMT

    [ http://jira.codehaus.org/browse/MCHECKSTYLE-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122193
] 

Dennis Lundberg commented on MCHECKSTYLE-64:
--------------------------------------------

I think that this is no longer an issue, because of the solution of MCHECKSTYLE-40. The build
output directory is now included in the class path available to Checkstyle. The package.html
files in src/main/javadoc do get copied to the build output directory, don't they?

You can try using the latest 2.2-SNAPSHOT version of this plugin.

> Allow inclusion of javadoc source path in check
> -----------------------------------------------
>
>                 Key: MCHECKSTYLE-64
>                 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-64
>             Project: Maven 2.x Checkstyle Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.1
>            Reporter: Johan Vanbockryck
>            Priority: Minor
>
> According to the documentation of the maven-javadoc-plugin, the Javadoc resources (like
package.html) should be placed in src/main/javadoc. This will cause a checkstyle error for
missing package.html files however when enabling the PackageHtml module, since this directory
is not included in the checkstyle source path.
> See also: http://maven.apache.org/plugins/maven-javadoc-plugin/faq.html

-- 
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

        

Mime
View raw message