[
http://jira.codehaus.org/browse/MJAVADOC-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120314
]
Vincent Siveton commented on MJAVADOC-166:
------------------------------------------
Links are broken. Could you attache your log files?
I checkout your project, uncomment the section, and call "mvn site" => Build
successful.
BTW, calling javadoc:javadoc doesn't call javadoc:test-javadoc, it is 2
separate goals [1]
"mvn site:site" calls the site plugin and "mvn site" calls the site lifecycle.
[1] http://maven.apache.org/plugins/maven-javadoc-plugin/plugin-info.html
> javadoc:javadoc fails within site lifecycle
> -------------------------------------------
>
> Key: MJAVADOC-166
> URL: http://jira.codehaus.org/browse/MJAVADOC-166
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Reporter: Michael Osipov
>
> I have my pom.xml configured creating a javadoc report upol "site" goal
> this is my project:
> http://dev.fckeditor.net/browser/FCKeditor.Java/branches/2.4
> this is my pom.xml:
> http://dev.fckeditor.net/browser/FCKeditor.Java/branches/2.4/pom.xml
> (reported is commented out since it produces problems)
> console log solely running: javadoc:javadoc http://rafb.net/p/U0KqMb29.html
> works perfectly
> the documentation of javadoc plugin says that if I include it to the
> reporting part of my pom, it will atuomatically produce javadoc for my main
> java stream, well this is what happends: http://rafb.net/p/7xREXc27.html
> Do you see the diffrence?
> 1. It generates testdocs for some reason, too
> 2. it says it can't resolve types and classes which did not happen with
> javadoc:javadoc
> I guess, this is a bug
--
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
