Hanson Char wrote:
> Here is the stack trace from ant -debug. (Also attached is the complete log
> of the build.)
Thanks. It's interesting, as some other javadoc tasks seem to be working
fine. Only this particular invocation is causing an issue.
I noticed that in the stack trace, at the end of the stack trace,
there's a character whose code is 0x94 (not a valid ASCII char, I
think.) Perhaps this might be related, but I don't know where it came from.
> --- Nested Exception ---
> java.io.IOException: CreateProcess: C:\Software\jdk\1.5.0\06\bin\javadoc.exe -quiet -d C:\Playground\workspace\3.1.1\jaxb2-sources\jaxb-ri\runtime\build\api -use -windowtitle "JAXB RI runtime" -package -classpath C:\Playground\workspace\3.1.1\jaxb2-sources\jaxb-ri\runtime-api\build\classes;C:\Playground\workspace\3.1.1\jaxb2-sources\jaxb-ri\tools\lib\redist\activation.jar;C:\Playground\workspace\3.1.1\jaxb2-sources\jaxb-ri\tools\lib\redist\jaxb-api.jar;C:\Playground\workspace\3.1.1\jaxb2-sources\jaxb-ri\tools\lib\redist\jsr173_1.0_api.jar;C:\Playground\workspace\3.1.1\jaxb2-sources\jaxb-ri\tools\lib\rebundle\compiler\dtd-parser-1.0.jar;C:\Playground\workspace\3.1.1\jaxb2-sources\jaxb-ri\tools\lib\rebundle\compiler\relaxngDatatype.jar;C:\Playground\workspace\3.1.1\jaxb2-sources\jaxb-ri\tools\lib\rebundle\compiler\resolver.jar;C:\Playground\workspace\3.1.1\jaxb2-sources\jaxb-ri\tools\lib\rebundle\compiler\rngom.jar;C:\Playground\workspace\3.1.1\jaxb2-sources\jaxb-ri\tools\li
b\rebundle\compiler\xsom.jar;C:\Playground\workspace\3.1.1・
Another possibility is that it might be related to this:
http://jira.codehaus.org/browse/MPJAVADOC-11?decorator=printable
Could you try the suggested workaround by adding useexternalfile="yes"
to the javadoc task that's dying?
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com