On 5/24/15, 11:21 PM, "Frédéric THOMAS" wrote:
>
>> I seem to recall messing around with CompilerConfiguration when
>> integrating with FB. So there may already be code that maps it to the
>> Falcon configurations.
>
>Yes (well if I get you correctly) but with other package which then don't
>wo
> Excellent! I assume that COMPC uses flex2/tools/oem/Library.java
Nope, I don't if I do well but I mapped what was before, a call to COMPC as I
do for Mxmlc which is what IJ expect.
> I seem to recall messing around with CompilerConfiguration when
> integrating with FB. So there may already b
On 5/24/15, 8:09 AM, "Frédéric THOMAS" wrote:
>Hi Alex,
>
>> IIRC, the FB compiler calls flex2/tools/oem/Application.java. You can
>>see
>> how this class builds up an OEMReport with messages.
>
>Thanks, I've been able to create and OEMReport based on that.
>
>So, at the moment, using the Mxml
Great, I nominate you to fix all Mustella tests going forward ;-)
On May 23, 2015 9:52 PM, "Alex Harui" wrote:
> Well, I must have magical powers because I did some digging last night and
> upon running a test that failed in the main SDK run in FDB, it passed.
> Then I restarted the main SDK run
Hi Alex,
> IIRC, the FB compiler calls flex2/tools/oem/Application.java. You can see
> how this class builds up an OEMReport with messages.
Thanks, I've been able to create and OEMReport based on that.
So, at the moment, using the Mxml entry point they use, plug into the MCMLC and
sending old
