db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dyre Tjeldvoll (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-249) Builds fail during splitmessages step if path contains spaces
Date Fri, 13 May 2005 09:14:34 GMT
     [ http://issues.apache.org/jira/browse/DERBY-249?page=comments#action_65270 ]
Dyre Tjeldvoll commented on DERBY-249:

This happens because the ANT-task that runs the splitmessages.java program supplies the two
arguments (a directory and a property file) with a <arg line="..."/> element. 

The ANT manual (http://ant.apache.org/manual/), says "Ant will try to split the command line
in a way similar to what a (Unix) shell would do, but may create something that is very different
from what you expect under some circumstances."
And that is what happens. With spaces in the file names the shell-like splitting will cause
splitmessages.java to be started with more than two arguments.

The solution is to replace the <arg line="..."/> element in java/engine/org/apache/derby/loc/build.xml
with a pair of <arg value="..."/> elements. 

> Builds fail during splitmessages step if path contains spaces
> -------------------------------------------------------------
>          Key: DERBY-249
>          URL: http://issues.apache.org/jira/browse/DERBY-249
>      Project: Derby
>         Type: Bug
>   Components: Build tools
>     Versions:,
>     Reporter: Samuel Andrew McIntyre
>     Assignee: Dyre Tjeldvoll
>     Priority: Trivial

> If the path to the Derby source files contains a space, for example /opt/My Local Drive/derbysource,
then the build will fail at the splitmessages step with the following error:
>      [java] Exception in thread "main" java.lang.StringIndexOutOfBoundsException: String
index out of range: -1
>      [java]     at java.lang.String.substring(String.java:1444)
>      [java]     at org.apache.derbyBuild.splitmessages.main(splitmessages.java:44)
> splitmessages should be improved to handle spaces in the path to the message files.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message