|
Sort Order:
I do not believe that the options file is the trouble maker, it is not found by javadoc.
To me, it seems rather like a problem with Plexus' CommandLineUtils and related classes. From public String getExecutable() { File wd = getWorkingDirectory(); if ( wd != null ) { String path = getWorkingDirectory().getAbsolutePath(); String exe = super.getExecutable(); return "cd " + handleQuote( path ) + " && " + handleQuote( exe ); } else { return super.getExecutable(); } } They do not seem to care about spaces in the pathes. I am not sure, but it could result in the effective command working directory "/Users/clabu/Documents/workarea/Elk", where no options or package files exist. I'm having the same issue on 2 different versions of Linux (RedHat AS4 & Suse 10.2) with version 2.4 of the plugin. If I use the 2.0 version the problem does not occur.
Vincent Siveton made changes - 29/May/08 05:56 PM
It seems to be related to the changes work for me, however I now see a test failure in testQuotedPath on trunk: ------------------------------------------------------------------------------- Test set: org.apache.maven.plugin.javadoc.JavadocReportTest ------------------------------------------------------------------------------- Tests run: 20, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 30.902 sec <<< FAILURE! testQuotedPath(org.apache.maven.plugin.javadoc.JavadocReportTest) Time elapsed: 0.927 sec <<< ERROR! org.apache.maven.plugin.MojoExecutionException: An error has occurred in JavaDocs report generation:Exit code: 2 - /bin/sh: -c: line 0: unexpected EOF while looking for matching `'' /bin/sh: -c: line 1: syntax error: unexpected end of file Command line was:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc @options @argfile at org.apache.maven.plugin.javadoc.JavadocReport.execute(JavadocReport.java:226) at org.apache.maven.plugin.javadoc.JavadocReportTest.testQuotedPath(JavadocReportTest.java:517) Caused by: org.apache.maven.reporting.MavenReportException: Exit code: 2 - /bin/sh: -c: line 0: unexpected EOF while looking for matching `'' /bin/sh: -c: line 1: syntax error: unexpected end of file Command line was:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc @options @argfile at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJavadocMojo.java:1674) at org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:127) at org.apache.maven.plugin.javadoc.JavadocReport.execute(JavadocReport.java:222) ... 27 more
Vincent Siveton made changes - 04/Jun/08 06:29 PM
I updated p-u to 1.5.2-SNAPSHOT in r663590, snapshot deployed. Could you retry with javadoc plugin 2.5-SNAPSHOT? I've also the bug (linux platform, bash shell) with the 2.4 version. I just now tested the 2.5-SNAPSHOT version, and all is fine for the 'bug of the space'
Arnaud Heritier made changes - 18/Jul/08 06:55 AM
This issue is fixed with the update of plexus-util
Arnaud Heritier made changes - 18/Jul/08 06:55 AM
I was having the bug in Maven 2.0.9 in this configuration: <reporting> Simply forcing the 2.5 version fixed the problem for me: <reporting> |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bug
Closed
Major
Cannot generate Javadoc on Mac OS X if path contains space characters
Could you send us the options and packages files? You need to add -Ddebug=true.
http://maven.apache.org/plugins/maven-javadoc-plugin/faq.html#How%20to%20know%20exactly%20the%20Javadoc%20command%20line