Hi Alex,
that's strange ... Did you change to the falcon root directory and run maven directly from there? I am asking this, cause the extension mechanism of looking for the ".mvn/extensions.xml" file relative to the place the command is executed. When running in Jenkins for example I did have some problems as mvn was called from somewhere else and the path to the root pom.xml was passed in. In that case the extension didn't work. But I thought you said you executed the build and it worked yesterday? If it's downloaded once, there shouldn't be the need to re-download again. "-DskipTests" skips the test execution. The dependency resolution is done in another phase of Maven and therefore it still resolves test-dependencies. I intentionally didn't assume the default, as this is usually the first thing people change. And as soon as something is deployed in the maven local repo its there and stays there till you manually delete it. I didn't want to eventually mess up the local repos so I wrote in the documentation that the user should review the result and copy that to the local repo. However you provide the "-mavenDir" pointing to your maven local repo, you should be ready to go. Chris ________________________________ Von: Alex Harui <aha...@adobe.com> Gesendet: Mittwoch, 22. Juni 2016 00:09:06 An: dev@flex.apache.org Betreff: Re: AW: [Falcon][FlexJS] Help with finishing the maven migration I copy/pasted the command-lines from your email and still needed to run the converter. I had never converted any Flex SDK before, so maybe there is some assumption somewhere. I know the Flex SDK is required to run some integration tests but I had set -Dskiptests and it still wanted the Flex SDK. To convert the Flex SDK, I first installed Apache Flex 4.15.0 with AIR/FP 20.0. Then I tried running: java -jar apache-flex-sdk-converter-1.0.0-SNAPSHOT.jar -fdkDir /Users/aharui/ApacheFlex4.15.0 but it wanted me to add a -mavenDir parameter. I would have thought it could have guessed to use my local repo ~/.m2 -Alex From: Christofer Dutz <christofer.d...@c-ware.de<mailto:christofer.d...@c-ware.de>> Reply-To: "dev@flex.apache.org<mailto:dev@flex.apache.org>" <dev@flex.apache.org<mailto:dev@flex.apache.org>> Date: Tuesday, June 21, 2016 at 2:19 AM To: "dev@flex.apache.org<mailto:dev@flex.apache.org>" <dev@flex.apache.org<mailto:dev@flex.apache.org>> Subject: 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<mailto:aha...@adobe.com>> Gesendet: Dienstag, 21. Juni 2016 08:10:05 An: dev@flex.apache.org<mailto: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<mailto: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
