Flex4 automated builds and license key

Question

When working in Flex3, we were able to include the following configuration file with the license key:
<flex-config>
    <licenses>
        <license>
            <product>flexbuilder3</product>
            <!--professional-->
            <serial-number>1234-1234-1234-1234-1234-1234</serial-number>
        </license>
    </licenses>
</flex-config>
Testing in Flex4, my QA person reports that he receives a message saying:  "License not prestent.  With teh trial version only limited replays are allowed " when QTP executes their tests.
I had fashioned a config file after the one we used in our Flex3 build for Flex4:
<flex-config>
    <licenses>
        <license>
            <product>flashbuilder4</product>
            <serial-number>1234-1234-1234-1234-1234-1234</serial-number>
        </license>
    </licenses>
</flex-config>
In the examples I have found on Adobe's site for Flex for they all just say to specify the product name.  I guessed based on Flex3 name that it should be flashbuilder4.  This was a guess on my part since I haven't found an actual example.  Does anyone have any suggestions on inserting a licnense key for Flex 4 in an ANT build?
--Thanks

Answer 1

Actually, mxmlc and fcsh ARE standard Adobe products.  They come with the SDK.  More importantly, they are free, so you can compile your flex apps without a license key.  You could hack together a build server using a cron job to fire up a bash script to pull down your release from svn, then invoke the mxmlc compiler (./mxmlc ....) and deploy the file.  One of the projects I was able to build using Hudson/maven, I'm not sure on the specifics though.