[jira] Commented: (MJAVADOC-181) Javadoc report not generated for multi-module project if run from parent level.
[ http://jira.codehaus.org/browse/MJAVADOC-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250849#action_250849 ] André Fügenschuh commented on MJAVADOC-181: --- @ Herve You are right. I don't know the IT, but the original intention was to *aggregate* javadocs at 'library' level (for 'module-\[a|b\]') and generate _non-aggregate_ javadocs for 'application'. As for me, this issue hasn't been resolved, see: [MSITE-518|http://jira.codehaus.org/browse/MSITE-518]. > 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 >Assignee: Vincent Siveton > Fix For: 2.6 > > Attachments: maven-site-javadoc-testcase.zip, > maven_release_failure_caused_by_mjavadoc.txt, 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
[jira] Commented: (MJAVADOC-181) Javadoc report not generated for multi-module project if run from parent level.
[ http://jira.codehaus.org/browse/MJAVADOC-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250443#action_250443 ] Herve Boutemy commented on MJAVADOC-181: I don't understand: the IT generates apidocs in module-a and module-b but not in library IIUC, the expected result was the contrary, no? can someone confirm that the actual result with maven-javadoc-plugin 2.6 and 2.7 is really what was expected? (FYI, I'm running into trouble with MJAVADOC-286, where the fix breaks the actual behaviour, and the more I think at it, the more I'm convinced this issue IT checks the contrary to the expected result...) > 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 >Assignee: Vincent Siveton > Fix For: 2.6 > > 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
[jira] Commented: (MJAVADOC-181) Javadoc report not generated for multi-module project if run from parent level.
[ http://jira.codehaus.org/browse/MJAVADOC-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153658#action_153658 ] Julien HENRY commented on MJAVADOC-181: --- It is a blocker issue for me. I can't use the old way because my generated source files are not taken into account. The new way is working when running mvn javadoc:aggregate but not when running mvn site. Please apply the patch and release a new version! > 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
[jira] Commented: (MJAVADOC-181) Javadoc report not generated for multi-module project if run from parent level.
[ http://jira.codehaus.org/browse/MJAVADOC-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148735#action_148735 ] Felix Knecht commented on MJAVADOC-181: --- IMO this is not a major issue but a blocker, because it avoids using the newer, non deprecated configuration of the javadoc plugin. Regards Felix > 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
[jira] Commented: (MJAVADOC-181) Javadoc report not generated for multi-module project if run from parent level.
[ http://jira.codehaus.org/browse/MJAVADOC-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148239#action_148239 ] James William Dumay commented on MJAVADOC-181: -- I can confirm that this is also a problem > 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 > > > 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
