Hmm, installing the latest javadoc plugin from svn into my local
repository solves the problem. I had beta-1, and I installed beta-3.
I wonder why this didn't happen automatically. Other plugins appear
to update automatically.
Thanks,
J
On 24-Oct-05, at 3:00 PM, Julian Wood wrote:
Javadoc creation is failing for me, simply because the javadoc
command is being invoked incorrectly. It would appear that it has
something to do with the way plexus is locating commands, but I'm
not sure.
Embedded error: An error has occurred in javadoc report generation.
/System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home/../
bin/javadoc: not found
...
Caused by: java.io.IOException: /System/Library/Frameworks/
JavaVM.framework/Versions/1.4.2/Home/../bin/javadoc: not found
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.<init>(UNIXProcess.java:54)
at java.lang.Runtime.execInternal(Native Method)
at java.lang.Runtime.exec(Runtime.java:566)
at org.codehaus.plexus.util.cli.Commandline.execute
(Commandline.java:674)
It should be coming up with
/System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home/bin/
javadoc
or even
/usr/bin/javadoc
since that's what my JAVA_HOME env var is defined as.
Is there a setting I'm missing somewhere? Curiously, other
invocations of java tools (ie javac) are invoked properly. This has
been the same from m2a3 up to the current mvn2 release.
Thanks,
J
--
Julian Wood <[EMAIL PROTECTED]>
Programmer/Analyst
University of Calgary
http://commons.ucalgary.ca
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Julian Wood <[EMAIL PROTECTED]>
Programmer/Analyst
University of Calgary
http://commons.ucalgary.ca
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
