[ https://issues.apache.org/jira/browse/DERBY-6071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13578048#comment-13578048 ]
Myrna van Lunteren commented on DERBY-6071: ------------------------------------------- committed the change with revision 1445994 (http://svn.apache.org/viewvc?view=revision&revision=1445994) > trunk javadoc build fails with Javadoc failed: java.io.IOException: Cannot > run program \bin\javadoc.exe": CreateProcess error=206, The filename or > extension is too long. > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-6071 > URL: https://issues.apache.org/jira/browse/DERBY-6071 > Project: Derby > Issue Type: Bug > Components: Build tools > Affects Versions: 10.10.0.0 > Environment: Windows 7 > Reporter: Myrna van Lunteren > Fix For: 10.10.0.0 > > > With trunk svn updated to revision 1445458, the javadoc build on windows > fails with an error like: > [path_to_trunk]\build.xml:1388: Javadoc failed: java.io.IOException: > Cannot run program "[path_to_ibm16jvm]\bin\javadoc.exe": CreateProcess > error=206, The filename or extension is too long. > This is in the testingdocs target. > It appears a new test causes the javadoc name to be too long for windows > javadoc. > The solution is to add a property, 'useexternalfiles=yes'. > Other javadoc targets, e.g. derbydocs and demodocs, already have this > property. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira