flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: [Falcon][FlexJS] Help with finishing the maven migration
Date Tue, 21 Jun 2016 06:10:05 GMT

On 6/20/16, 1:39 AM, "Christofer Dutz" <christofer.dutz@c-ware.de> wrote:

>I have finished migrating Falcon to Maven and all except the XML
>framework module of ASJS seem to be migrated too. I do need some help
>with getting the examples up and running and finding out why the js
>version of XML isn't working. I know that it worked a few days/1-2 weeks
>ago, but I have no idea why it's no longer working. A lot seems to have
>been changed with the configuration of the JS builds, so I would like to
>ask the people working on this to have a look.

The compiler build failed with:

[ERROR] Failed to execute goal on project compiler: Could not resolve
dependencies for project
org.apache.flex.flexjs.compiler:compiler:jar:0.7.0-SNAPSHOT: The following
artifacts could not be resolved:
org.apache.flex.framework:framework:zip:configs:4.15.0: Failure to find
com.adobe.flash.framework:playerglobal:swc:20.0 in
https://repository.apache.org/content/repositories/releases was cached in
the local repository, resolution will not be reattempted until the update
interval of apache-release has elapsed or updates are forced -> [Help 1]

I finally figured out how to get around it by using flex-sdk-converter to
convert a 4.15.0 SDK, but it made me wonder:
1) Why does the compiler build need Flex SDK?
2) Why does the converter not assume the -mavenDir is the Maven Local Repo?

After that, the falcon build finished as expected as did the asjs build,
so congratulations there!

The XML compile that uses compile-extern-config.xml doesn't seem to be
using the -compiler.strict-xml=true option.

The DataBindingExample-SNAPSHOT.swf failed with an error about "native"
code.  I noticed that in the XML compile-extern-config.xml that the js
extern is in the library path instead of external library path, which
might not cause a problem until you try to run a SWF.


View raw message