On 10/11/14, 7:01 PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>Hi, > >> How were you planning on adding the flexunit? By changing >>installer.xml? > >I would add this to the Flex SDK steps so that it show up as an optional >component. > <component id="STEP_REQUIRED_INSTALL_APACHE_FLEX_UNIT" required="false" >property="do.flexunit.install"> > ... > </component> > >What I then intended was have the installer run FlexUnits installer.xml >script, but if that can't do a MD5 check then I'll have to come up with >another way of doing it. Adding a step only sets a flag. What code was going to react to that flag? If it is the 3.2 Installer, it could certainly do the MD5 check before launching the FlexUnit install. If you are going to change the SDK’s installer.xml to look for that flag, you can the installer.xml pull the binary from dist/mirror and also pull the md5 file from dist and compare. Then you aren’t baking MD5 values into the installer.xml. Somewhere there is already ant code that does that. I can go find it for you if needed. -Alex
