[ http://jira.codehaus.org/browse/MNG-909?page=comments#action_46594 ]
Daniel Schömer commented on MNG-909: ------------------------------------ Sorry, I've set the scope of my dependencies to "runtime" instead of "compile". After setting the scope to "compile", the javadoc classpath is set correctly. Please close this issue. I'm very sorry for the inconvenience. > Include project dependencies to javadoc classpath > ------------------------------------------------- > > Key: MNG-909 > URL: http://jira.codehaus.org/browse/MNG-909 > Project: Maven 2 > Type: Improvement > Components: maven-javadoc-plugin > Versions: 2.0-beta-1 > 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]
