On Mon, Oct 20, 2014 at 4:50 PM, Alex Harui <aha...@adobe.com> wrote:
>
>
> On 10/20/14, 4:22 PM, "OmPrakash Muppirala" <bigosma...@apache.org> wrote:
>
> >
> >How did these kind of errors pass through the daily builds?
> That’s a good question. What do you mean by “FB caught these compile
> errors”?
I don't see these errors caught when I compile the FlexJSUI swc using the
command line. But, when I open up the source code in an FB Flex Library
project, these errors are caught.
> How are you set up to compile?
I have two Flex Library projects, one for FlexJSUI and one for FlexJSJX.
The projects have their main source folders set to
git/flex-asjs/frameworks/as/projects/{ProjectName}/src. FlexJSJX has a
'project dependency' on FlexJSUI in the build path settings. Both of them
are compiled using the Flex SDK 4.13 compiler. I add the basic library
manifest namespace to both projects via 'Additional Compiler arguments'.
So, my changes to FlexJSUI and FlexJSJX are checked by FB as I type.
My FlexJS app project is a setup in FB to use the FlexJS SDK installed
using the Installer.
When I am ready to test the changes to FlexJSUI and FlexJSJX on my FlexJS
app project, I run ant in the flex-asjs\frameworks\as. Then I copy over
the swcs generated under flex-asjs\frameworks\as\libs into my
FlexJS_via_Installer\frameworks\as\libs folder.
Then I just do a clean, rebuild of my FlexJS app.
> In theory, FlexJS code is no
> longer compiled by MXMLC, but I’m guessing you are somehow set up to do
> so. Falcon still has bugs and isn’t catching these things (yet). It
> would be better to fix Falcon to report the error before fixing the AS
> code, but I’m sure I'll hit these patterns again later and fix it then.
>
>
Ah, so these are Falcon bugs which are getting caught by the older mxmlc.
I will do my best to create JIRA tickets for such issues I find in future.
Thanks,
Om
> -Alex
>
>
