I was having problems with "windowisms" such as spaces and \r's when running the build.sh. The easy fix was for the jar command. The more complex one is for the revision number. I replaced the grep with a sed command because I was getting 98\r when it gets to the printf command later. Seems to work on windows, I may also check it on linux.
--- build.sh (revision 98)
+++ build.sh (working copy)
@@ -9,10 +9,10 @@
local last_rev
# Generate a release number for the entire branch
- last_rev=$(svn info $1 2>&1 | grep 'Last Changed Rev')
- pkg_release=${last_rev#Last Changed Rev: }
+ pkg_release=$(svn info $1 2>&1 | sed -n -e "s/Last Changed Rev: \([0-9]\+\).*\$/\\1/p")
+
if [ -z "$pkg_release" ] ; then
- pkg_release=0
+ pkg_release=0
fi
# Left pad with zeroes to 6 columns
printf "%06d" ${pkg_release}
@@ -58,7 +58,7 @@
# make the chrome jar
pushd build/$BASE/chrome > /dev/null
rm -f ec2ui.jar
- $JAVA_HOME/bin/jar cf ec2ui.jar content locale skin
+ "$JAVA_HOME/bin/jar" cf ec2ui.jar content locale skin
popd > /dev/null
# prepare source for bundling