How to use fcshWrapper

Download the binaries [FCSH Wrapper 0.1.2], unpack to any directory you want. Specify FCSHWRAPP_HOME property to point to the directory where you unpacked the binaries, FLEX_HOME to your flex sdk directory. FCSHWRAPP_JRE and FCSHWRAPP_PORT are not mandatory.

FCSHWRAPP_JRE must point to a jre 1.5 or higher, but if it is not specify, the jre used to lunch the wrapper will be searched in JAVA_HOME then JRE_HOME. If none of these are specified, it relays on the system PATH to lunch the wrapper. The default port on which the wrapper accepts commands is 52795. If you wont another port you can specify it on the FCSHWRAPP_PORT property.

A sample build file using fcshWrapper:

testScript.xml

<?xml version="1.0" encoding="UTF-8"?>
<project name="changeme" default="all" basedir=".">
   <property name="FCSHWRAPP_PORT" value="52797"/>
   <property name="FCSHWRAPP_JRE" value="C:/Program Files/Java/jdk1.5.0_11"/>
   <property name="FCSHWRAPP_HOME" value="d:/fcshWrapper-bin/bin"/>
   <property name="FLEX_HOME" value="c:/flex-sdk"/>
  
   <path id="mypath">
       <fileset dir="${FCSHWRAPP_HOME}" includes="fcshWrapper.jar"/>
   </path>
  
   <taskdef name="fcsh" classname="ro.arhinet.fcshwrapper.ant.FcshTask">
       <classpath refid="mypath"/>
   </taskdef>
  
   <target name="all">
       <fcsh command="mxmlc">
           <arg value="c:\ArhiNET.project\arhinet\web\flex-pages\app1.mxml"/>
           <arg value=" "/>
       </fcsh>
   </target>
</project>

Unfortunately I have build the application to work only on windows, but with some minor changes (another jdic binaries and removing '.exe' hardcoded calls in code) can be made to run on any other platform.

The first time the ant task is called, it observes that nobody is listening on the specified port and auto-lunches the wrapper as a separate process that can be observed on the system tray.

The output of the fcsh.exe is redirected to the ant task. The ant task fails if there is an error compiling flex files. The fcshWrapper remember the commands received and their assigned ids by the fcsh.

The wrapper stays on the system tray and notifies you when the build fails.

And there is also a console with all the commands received by the wrapper that can be hided/displayed from the system tray.