Ok so I made sure the js-extern is added to the external library path of all modules, but it seems that I still am getting the same error message:
VerifyError: Error #1079: Native methods are not allowed in loaded code. Would be grateful for some help to what's causing this. Chris ________________________________ Von: Christofer Dutz <christofer.d...@c-ware.de> Gesendet: Dienstag, 21. Juni 2016 11:19:32 An: dev@flex.apache.org Betreff: AW: [Falcon][FlexJS] Help with finishing the maven migration Hi Alex, If you used the "settings-template.xml" it should have used the sdk converter automatically (You should see an ASCII Art Flex logo in the the build in that case). I didn't add the dependency to the FlexSDK it was the Ant build that needed some of the libraries there. I think I remember some of the Falcon unit tests, requiring the Flex SWCs for building. (See ASFeatureTestBase) I don't quite understand what you mean with "-mavenDir". I only wanted to put in the settings-template what is needed. When using this in a jenkins job, it was counterproductive to set the maven local repo home, so I stick to the defaults. I added "strict-xml=true" to all externs and it seemed to have worked nicely ... thanks for that. Even if I thought I had already added that. Oh well ... if it works, it's good [?] So now all the Framework libs seem to be ok. Will look into the Examples and the js dependency later on ... Thanks ... Chris ________________________________ Von: Alex Harui <aha...@adobe.com> Gesendet: Dienstag, 21. Juni 2016 08:10:05 An: dev@flex.apache.org Betreff: Re: [Falcon][FlexJS] Help with finishing the maven migration On 6/20/16, 1:39 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >Hi, > > >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: com.adobe.flash.framework:playerglobal:swc:20.0, org.apache.flex.framework:framework:swc:4.15.0, org.apache.flex.framework:rpc:swc:4.15.0, org.apache.flex.framework:spark:swc:4.15.0, 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. HTH, -Alex
