flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: AW: AW: AW: [FlexJS] Status on Maven migration
Date Fri, 22 Apr 2016 19:30:49 GMT
By downloading the subset of swfutils, I was able to complete
flex-compiler-oem and debugger.  Next up is to test the "all" target and
then release packaging.

-Alex

On 4/22/16, 10:32 AM, "Alex Harui" <aharui@adobe.com> wrote:

>OK, I have finished re-creating the Ant builds for compiler, and
>compiler-jx and externs and pushed those changes.  Hopefully I didn't
>break the Maven build.  AFAIK, I did not change any file locations or
>names.
>
>Since we are downloading externs files, I think I am going to download the
>swfutils files and use those to complete flex-compiler-oem and debugger.
>I'll bake them right into those jars, so no separate swfutils.jar.
>
>FWIW, we could merge now, but the nightly builds would be broken.
>
>-Alex
>
>On 4/22/16, 9:35 AM, "Alex Harui" <aharui@adobe.com> wrote:
>
>>
>>
>>On 4/22/16, 1:11 AM, "Christofer Dutz" <christofer.dutz@c-ware.de> wrote:
>>
>>>I'm currently just pulling the jar from the latest SDK release ...
>>>anything wrong with that?
>>
>>IIRC, swfutils may have other dependencies on Flex SDK jars and end up
>>pulling lots of stuff in, including classes I'm trying to replace with
>>versions of mxmlc and compc that proxy in to Falcon.  I was able to find
>>this subset of swfutils that works for both flex-compiler-oem and
>>debugger
>>and doesn't bring in un-needed stuff.  I couldn't find swfutils in maven
>>central or a pom.xml for it to see what its dependencies are.
>>
>>I also found another issue: the externs/createjs project was running
>>externc twice, once with the js-root option.  I remembered as I was
>>working on that part of the Ant build that the reason it is called twice
>>is to "sanitize" the .js files before they are put into the SWC so that
>>the Google Closure Compiler will correctly use them as externs files.
>>The
>>CreateJS source files are brought down, munged with various replace/sed
>>tasks into a state where ExternC can use them to create .as files, but
>>later in the workflow, the Google Closure Compiler wants more cleanly
>>formatted .js files to use as externs during minification/optimization.
>>
>>So I was thinking of directing the output of the js-root pass to
>>target/generated-sources/externs, and modifying the compile-as-config.xml
>>to pick up the <include-files> from there.  Is that ok?
>>
>>Thanks,
>>-Alex
>>
>>
>

Mime
View raw message