maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fol De Rol (JIRA)" <>
Subject [jira] Created: (MJAVADOC-179) Aggregate report ignores sourcepath customization of subprojects
Date Tue, 26 Feb 2008 11:50:28 GMT
Aggregate report ignores sourcepath customization of subprojects

                 Key: MJAVADOC-179
             Project: Maven 2.x Javadoc Plugin
          Issue Type: Bug
    Affects Versions: 2.3
         Environment: Maven 2.0.8, Java 1.5, Windows
            Reporter: Fol De Rol

When using aggregate javadoc reporting with one of subproject being customized to include
java sources from alternative directories, only original source directories are passed to
javadoc executable.

For instance, I use POJO's generated by Hibernate3 from HBM files which are documented. The
generated files are placed into ${basedir}/target/hibernate3/generated-sources/ directory.
My subproject's POM contains the following definition:


and it works correctly if running {{mvn site}} on subproject level. If run from the parent
project, as I traced, the custom directory does not passed to the javadoc tool.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message