Hi Dennis,
The ${project.reporting.outputDirectory}/apidocs is the working directory,
whereas the javadoc executable is used with its absolute path.
So in the end it will often be:
cd ${project.reporting.outputDirectory}/apidocs
%JAVA_HOME%\bin\javadoc.exe @options @packages | @argfile
I say often, because there's toolchains and other ways to change the path
of the javadoc.exe
So yes, the docs are kind of wrong here
Robert
Op Sun, 21 Jul 2013 17:25:08 +0200 schreef Dennis Lundberg
<[email protected]>:
Hi
I got sidetracked by this and cannot let go of it. On the index page
of Maven Javadoc Plugin
http://maven.apache.org/plugins/maven-javadoc-plugin/
it says this:
-----
...the Javadoc Plugin generates argument files and calls the Javadoc
tool as follow:
#${project.reporting.outputDirectory}/apidocs/javadoc.exe(or .sh) \
@options @packages | @argfile
-----
This does not make any sense at all to me. If I were to run that
command on the command line, my Windows machine would say some along
the lines of
"...target\site\apidocs\javadoc.exe is not a command"
This is also in the FAQ at
http://maven.apache.org/plugins/maven-javadoc-plugin/faq.html#How_to_know_exactly_the_Javadoc_command_line
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
