[icedtera-web] future of shell launchers

[Jiri Vanek]

Hi Laurent!

Maybe a bit more constructive answer to you query.
You could noticed, than in rust lunchers(patch still on review), we are not using make-generated
classpath, but instead are sent in individual jars.
I think they are much more versatile for various changes of paths.
usage of those will make (boot)classpaths composing in bats easier, and allows better implementation
of ITW_HOME into linux shells.
I have very good experience with resolvig scripts dir with following snippet[1].
So the workflow can be:
1)adding [1] to both head and 1.7
2)change shell launchers in 1.8 to accept parameters whcih are flowing to rust lunchers
3)in 1.8 compose classapths honor variables in same manner as rust lucnhers do
4)adapt non breakig parts of 2 an 3  in 1.7. namely hack (sed in (boot)cps>) the usage og  [1]'s
SCRIPT_DIR and  bat's ITW_HOME
  - postpond posisble dangerous parts to 1.7.3
In meantime, finish .args file handling everywhere. Especially in 1.8.

Thoughts?


[1]
## resolve folder of this script, following all symlinks,
## http://stackoverflow.com/questions/59895/can-a-bash-script-tell-what-directory-its-stored-in
SCRIPT_SOURCE="${BASH_SOURCE[0]}"
while [ -h "$SCRIPT_SOURCE" ]; do # resolve $SOURCE until the file is no longer a symlink
  SCRIPT_DIR="$( cd -P "$( dirname "$SCRIPT_SOURCE" )" && pwd )"
  SCRIPT_SOURCE="$(readlink "$SCRIPT_SOURCE")"
  # if $SOURCE was a relative symlink, we need to resolve it relative to the path where the symlink
file was located
  [[ $SCRIPT_SOURCE != /* ]] && SCRIPT_SOURCE="$SCRIPT_DIR/$SCRIPT_SOURCE"
done
readonly SCRIPT_DIR="$( cd -P "$( dirname "$SCRIPT_SOURCE" )" && pwd )"
-- 
Mgr. Jiri Vanek
judovana at email.cz