[
http://jira.codehaus.org/browse/MSITE-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=241140#action_241140
]
André Fügenschuh commented on MSITE-518:
----------------------------------------
Some further investigations:
1)
Using {{mvn site}} apidocs *are* generated at (*wrong*)
_library.modules-\[a|b\]_ level,
using {{mvn site:stage}} _library_'s apidocs are *not* generated at all.
Caused by automatic (inherited?) invocation at the very end of the reactor run:
{noformat}
...
[INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:2.7:javadoc'
has not be previously called for the project:
'foo.library:module-a:jar:3.0-SNAPSHOT'.
Trying to invoke it...
[INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:2.7:javadoc'
has not be previously called for the project:
'foo.library:module-b:jar:3.0-SNAPSHOT'.
Trying to invoke it...
...
{noformat}
2)
Trying to break inheritance in the _library_ pom with the {{<inherited>}}
element, it appears that it's not
allowed at any level: neither at _javadoc_ {{<reportPlugin>}} nor at its
{{<reportSet>}}.
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:site (default-site)
on project library: Unable to parse configuration of mojo
org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:site
for parameter plugin: Cannot find setter nor field in
org.apache.maven.plugins.site.ReportPlugin for 'inherited' -> [Help 1]
...
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:site (default-site)
on project parent: Unable to parse configuration of mojo
org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:site
for parameter reportSet: Cannot find setter nor field in
org.apache.maven.plugins.site.ReportSet for 'inherited' -> [Help 1]
{noformat}
Question: is this a) by design, b) simply yet missing, or c) a bug?
> Aggregated javadoc report not generated for multi-module project at sub-level
> if run from parent level.
> -------------------------------------------------------------------------------------------------------
>
> Key: MSITE-518
> URL: http://jira.codehaus.org/browse/MSITE-518
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: inheritance, multi module
> Affects Versions: 3.0-beta-3
> Environment: Windows Vista x64, JDK 6u22, Maven 3.0
> Reporter: André Fügenschuh
> Attachments: maven3-site-javadoc-testcase.zip
>
>
> With a +multi-module project design+ (cf. attached testcase):
> {noformat}
> - parent (pom)
> + library (pom) // javadoc:aggregate
> + module-a (jar)
> + module-b (jar)
> + application (jar) // javadoc:javadoc
> {noformat}
> run
> {{mvn site}} | {{mvn -DstagingDirectory=\[dir\] site:stage}}
> at _parent_ level.
> +Result:+
> Aggregated javadocs for _library_ are *not* generated (but are properly done
> if {{mvn site}} is run at _library_ level itself), while javadocs at
> _application_ level are generated.
> OT: as appropriate {{<modules>}} sections are declared (cf. attached
> testcase), {{mvn compile}} runs as expected at _parent_ level.
> This is a follow-up to MJAVADOC-181, which, although marked as resolved, has
> never been working for me using the _old_ site/reports configuration for
> Maven 2.2.1 / Site plugin 2.1.1.
--
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
