Install
After downloading the installation bundle (Download) install by extracting the bundle and setting a single environment variable XMLSH to the installed location.xmlsh requires an installation of the Sun Java JRE or SDK version 1.6 or greater and assumes java is in the PATH.
Windows systems
Unzip the installation to any directory.Set a system, user, or command environment variable XMLSH to refer to the root directory of the installation.
set XMLSH=<full path to xmlsh directory>
If you want xmlsh to be found without specifying the full path, you will need to edit your PATH variable either in the system environment or at the command line to include the %XMLSH%\win32 directory, or create your own .bat file which calls %XMLSH%\win32\xmlsh.bat
set PATH=%PATH%;%XMLSH%\win32
Test the java version.
JRE or JDK 1.6 or greater is required. Try running your default java and verify it reports a 1.6 or greater JRE.java -version
It should report something like
java version "1.6.0_13" Java(TM) SE Runtime Environment (build 1.6.0_13-b03) Java HotSpot(TM) Client VM (build 11.3-b02, mixed mode, sharing)
If the version is 1.5 or less you need to update or install JRE (or JDK) 1.6. You can have multiple java installations on your system. By setting the PATH and JAVAHOME variables you can choose which one is used. See documentation at java.com for details.
cygwin on Windows
If you want to run xmlsh directly from cygwin you can either run the Windows xmlsh.bat file or as of 1.1.6 a cygwin xmlsh script is supplied.To run the cygwin xmlsh script ( $XMLSH/cygwin/xmlsh) you need to set the XMLSH variable to the Windows file path (in either windows or java notation) NOT the cygwin file path. That is, do *not* include "/cygdrive/" in the path. This is because Java doesnt know its running under cygwin so doesnt know what to think of /cygdrive/.
Also Java (being a windows program) still uses the ";" as the CLASSPATH separator not ":" like unix so a special cygwin start-up script is supplied with the correct separators and quoting required for cygwin.
Unix systems (Including Mac)
Unzip the installation to any directory.unzip xmlsh_<release>.zip
Set a system, user, or command environment variable XMLSH to refer to the root directory of the installation.
export XMLSH=<full path to xmlsh directory>
Convert to unix LF format. Sometimes CR's end up in this file. Make sure it is in unix format.
Many unix systems include the "dos2unix" command
dos2unix xmlsh
If not then tr works great
tr -d '\r' < xmlsh > temp mv temp xmlsh
Now the xmlsh script needs to be made executable
chmod a+x $XMLSH/unix/xmlsh
If you want xmlsh to be found without specifying the full path, you will need to edit your PATH variable in your profile or on command line to include the $XMLSH/unix directory, or create your own script file which calls $XMLSH/unix/xmlsh
export PATH=$PATH:$XMLSH/unix
Mac/OS Specific Instructions
JRE or JDK 1.6 or greater is required. Java 1.6 is available for MacOS from Apple in this downloadhttp://www.apple.com/downloads/macosx/apple/application_updates/javaformacosx105update1.html
However it does not "update" the existing Java 1.5, but rather installs to a new location.
You need to change your path after installing the update, or create a symbolic link to the java 1.6 command.
The default location for the Java 1.6 commmand on Mac OS 10.5 is
/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Commands/java
After you set your PATH to include /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Commands at the beginning, or create a symbolic link to /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Commands/java try running java and verify it reports a 1.6 or greater JRE.
Test the java version.
java -version
It should report something like
java version "1.6.0_13" Java(TM) SE Runtime Environment (build 1.6.0_13-b03-211) Java HotSpot(TM) 64-Bit Server VM (build 11.3-b02-83, mixed mode)
So if you extract xmlsh into c:\program files\xmlsh_0.0.1.4., then you need to add this path to your PATH environmental var:
c:\program files\xmlsh_0.0.1.4\win32
That way, when you type xmlsh at a command prompt, it resolves to the batch file that launches an xmlsh session (c:\program files\xmlsh_0.0.1.4\xmlsh.bat in my specific example).