[
http://jira.codehaus.org/browse/MJAVADOC-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148733#action_148733
]
felixk edited comment on MJAVADOC-181 at 9/22/08 2:27 PM:
----------------------------------------------------------------
The problem is that the deprecated aggregate is still validated even if the
latest (not deprecated) configuration using the aggregate goal is used. This
results in an unwanted
JavadocReport.canGenerateReport return=false, because aggregate (not set ->
default=false) and isAggregator=true (see JavadocReport.java:
/** [EMAIL PROTECTED] */
public boolean canGenerateReport()
{
boolean canGenerate;
if ( aggregate != isAggregator() )
{
canGenerate = false;
).
This configuration will never generate an aggregated javadoc.
Applied patch (MJAVADOC-181-1.patch) overwrites the canGenerateReport method.
Deprecated aggregate shall not be used if the newer goal is used.
was (Author: felixk):
The problem is that the deprecated aggregate is still validated even if the
latest (not deprecated) configuration using the aggregate goal is used. This
results in an unwanted
JavadocReport.canGenerateReport return=false, because aggregate (not set ->
default=false) and isAggregator=true (see JavadocReport.java:
/** [EMAIL PROTECTED] */
public boolean canGenerateReport()
{
boolean canGenerate;
if ( aggregate != isAggregator() )
{
canGenerate = false;
).
This configuration will never generate an aggregated javadoc.
Applied patch overwrites the canGenerateReport method. Deprecated aggregate
shall not be used if the newer goal is used.
> Javadoc report not generated for multi-module project if run from parent
> level.
> -------------------------------------------------------------------------------
>
> Key: MJAVADOC-181
> URL: http://jira.codehaus.org/browse/MJAVADOC-181
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Environment: W2K, JDK 6u5, Maven 2.0.8
> Reporter: André Fügenschuh
> Attachments: maven-site-javadoc-testcase.zip, MJAVADOC-181-1.patch,
> MJAVADOC-181.patch
>
>
> For the following project design (s. attached testcase):
> parent
> \- library // javadoc:aggregate!
> \- module-a
> \- module-b
> \- application
> javadoc report for 'library' is *not* generated (not invoked), if 'mvn site'
> is
> called at 'parent' level (but is properly done if run at 'library' level
> itself).
--
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
