[ http://jira.codehaus.org/browse/MJAVADOC-35?page=all ]
Maria Odea Ching moved MNG-909 to MJAVADOC-35:
----------------------------------------------
Version: (was: 2.0-beta-1)
Component: (was: maven-javadoc-plugin)
Workflow: jira (was: Maven)
Key: MJAVADOC-35 (was: MNG-909)
Project: Maven 2.x Javadoc Plugin (was: Maven 2)
> Include project dependencies to javadoc classpath
> -------------------------------------------------
>
> Key: MJAVADOC-35
> URL: http://jira.codehaus.org/browse/MJAVADOC-35
> Project: Maven 2.x Javadoc Plugin
> Type: Improvement
> Reporter: Daniel Schömer
> Priority: Minor
>
>
> When calling "m2 javadoc:javadoc", the classpath parameter of the javadoc
> tool only contains the target/classes/ directory. But if the project sources
> use external depencies (like log4j, jakarta commons, ...), the javadoc tool
> is not able to find the referenced classes of the dependencies and displays
> according warnings.
> The javadoc:javadoc goal should set the classpath of the javadoc tool to the
> target/classes/ directory and the project's dependencies in compile scope.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
