[jira] Closed: (MJAVADOC-179) Aggregate report ignores sourcepath customization of subprojects
[
http://jira.codehaus.org/browse/MJAVADOC-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MJAVADOC-179.
Resolution: Cannot Reproduce
Without any feedbacks, we can't help you.
Aggregate report ignores sourcepath customization of subprojects
Key: MJAVADOC-179
URL: http://jira.codehaus.org/browse/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:
{code:xml}reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.2/version
configuration
sourcepath$\{basedir\}/src/main/java;$\{basedir]}/target/hibernate3/generated-sources/sourcepath
/configuration
/plugin
/plugins
/reporting{code}
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:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MJAVADOC-179) Aggregate report ignores sourcepath customization of subprojects
[
http://jira.codehaus.org/browse/MJAVADOC-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MJAVADOC-179.
Resolution: Cannot Reproduce
I cant reproduce it with 2.4 and 2.5-SNAPSHOT. So, try with these versions and
feel free to reopen it if the pb is still there (Think to including a test
case...)
Thanks.
Aggregate report ignores sourcepath customization of subprojects
Key: MJAVADOC-179
URL: http://jira.codehaus.org/browse/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:
{code:xml}reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.2/version
configuration
sourcepath$\{basedir\}/src/main/java;$\{basedir]}/target/hibernate3/generated-sources/sourcepath
/configuration
/plugin
/plugins
/reporting{code}
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:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
