Re: AW: AW: AW: AW: [FlexJS] Status on Maven migration
On 4/23/16, 7:05 AM, "Alex Harui" wrote: > >> >>Regarding the merge ... I'm ready when you are. > >I want to verify the install of a nightly will work. Might take all >weekend to get that far. OK, I think the nightly will work now. I will take care of merging recent changes in the develop branch. -Alex
Re: AW: AW: AW: AW: AW: AW: [FlexJS] Status on Maven migration
Every swc in asjs should create a swc for swf and a swc for js with different compile flags. Downstream swcs need the platform specific api. Sent from my LG G3, an AT&T 4G LTE smartphone -- Original message-- From: Christofer Dutz Date: Sun, Apr 24, 2016 7:42 AM To: Alex Harui;dev@flex.apache.org; Subject:AW: AW: AW: AW: AW: AW: [FlexJS] Status on Maven migration Up till now I only have the falcon externs compiling ... they use falcon for this. Are there more externs in the ASJS package? Chris Von: Alex Harui Gesendet: Sonntag, 24. April 2016 16:11 An: Christofer Dutz; dev@flex.apache.org Betreff: Re: AW: AW: AW: AW: AW: [FlexJS] Status on Maven migration Asjs extern swc is written in ActionScript so it uses falcon to compile. Doesn't the final phase of flex falcon extern swc also use falcon? Sent from my LG G3, an AT&T 4G LTE smartphone -- Original message-- From: Christofer Dutz Date: Sun, Apr 24, 2016 3:17 AM To: dev@flex.apache.org; Subject:AW: AW: AW: AW: AW: [FlexJS] Status on Maven migration No I'm still quite far from finished with that. I am coming closer and closer, but still I need to do some work. Currently the Core module is not building. Haven't had the time to dig into that though cause I was stuck with merging falcon stuff. One thing I did notice two days ago, was that I have to compile ASJS with the Flex Tool Group "FlexJS" (that's in falcon-jx) and the externs are compiled using the group "Falcon" (that's in falcon). I would have expected the externs to be compiled using the falcon-jx compiler as the externs belong to the cross compilation tool-chain ... any reason why they don't compile using falcon-jx? Chris Von: Alex Harui Gesendet: Samstag, 23. April 2016 18:10 An: dev@flex.apache.org Betreff: Re: AW: AW: AW: AW: [FlexJS] Status on Maven migration Forgot to ask... On 4/23/16, 2:06 AM, "Christofer Dutz" wrote: >Regarding the double run externc ... I noticed this too ... but I think I >managed to get everything working with just one pass in the Maven build. >In order to get things running I compared the output with the final >output of the Ant JavaScript and re-engineered ALL of the replacement >operations. So eventually looking at the replacements of the maven build >could eliminate the need to run externc twice. OK, I guess I will someday switch to using your replace tools. I've been wondering if there is some other way we should be doing this. Should we just use patch files instead? > >Regarding the merge ... I'm ready when you are. Are you also done with flex-asjs? I haven't looked there at all yet. -Alex
AW: AW: AW: AW: AW: AW: [FlexJS] Status on Maven migration
Up till now I only have the falcon externs compiling ... they use falcon for this. Are there more externs in the ASJS package? Chris Von: Alex Harui Gesendet: Sonntag, 24. April 2016 16:11 An: Christofer Dutz; dev@flex.apache.org Betreff: Re: AW: AW: AW: AW: AW: [FlexJS] Status on Maven migration Asjs extern swc is written in ActionScript so it uses falcon to compile. Doesn't the final phase of flex falcon extern swc also use falcon? Sent from my LG G3, an AT&T 4G LTE smartphone -- Original message-- From: Christofer Dutz Date: Sun, Apr 24, 2016 3:17 AM To: dev@flex.apache.org; Subject:AW: AW: AW: AW: AW: [FlexJS] Status on Maven migration No I'm still quite far from finished with that. I am coming closer and closer, but still I need to do some work. Currently the Core module is not building. Haven't had the time to dig into that though cause I was stuck with merging falcon stuff. One thing I did notice two days ago, was that I have to compile ASJS with the Flex Tool Group "FlexJS" (that's in falcon-jx) and the externs are compiled using the group "Falcon" (that's in falcon). I would have expected the externs to be compiled using the falcon-jx compiler as the externs belong to the cross compilation tool-chain ... any reason why they don't compile using falcon-jx? Chris Von: Alex Harui Gesendet: Samstag, 23. April 2016 18:10 An: dev@flex.apache.org Betreff: Re: AW: AW: AW: AW: [FlexJS] Status on Maven migration Forgot to ask... On 4/23/16, 2:06 AM, "Christofer Dutz" wrote: >Regarding the double run externc ... I noticed this too ... but I think I >managed to get everything working with just one pass in the Maven build. >In order to get things running I compared the output with the final >output of the Ant JavaScript and re-engineered ALL of the replacement >operations. So eventually looking at the replacements of the maven build >could eliminate the need to run externc twice. OK, I guess I will someday switch to using your replace tools. I've been wondering if there is some other way we should be doing this. Should we just use patch files instead? > >Regarding the merge ... I'm ready when you are. Are you also done with flex-asjs? I haven't looked there at all yet. -Alex
Re: AW: AW: AW: AW: AW: [FlexJS] Status on Maven migration
Asjs extern swc is written in ActionScript so it uses falcon to compile. Doesn't the final phase of flex falcon extern swc also use falcon? Sent from my LG G3, an AT&T 4G LTE smartphone -- Original message-- From: Christofer Dutz Date: Sun, Apr 24, 2016 3:17 AM To: dev@flex.apache.org; Subject:AW: AW: AW: AW: AW: [FlexJS] Status on Maven migration No I'm still quite far from finished with that. I am coming closer and closer, but still I need to do some work. Currently the Core module is not building. Haven't had the time to dig into that though cause I was stuck with merging falcon stuff. One thing I did notice two days ago, was that I have to compile ASJS with the Flex Tool Group "FlexJS" (that's in falcon-jx) and the externs are compiled using the group "Falcon" (that's in falcon). I would have expected the externs to be compiled using the falcon-jx compiler as the externs belong to the cross compilation tool-chain ... any reason why they don't compile using falcon-jx? Chris Von: Alex Harui Gesendet: Samstag, 23. April 2016 18:10 An: dev@flex.apache.org Betreff: Re: AW: AW: AW: AW: [FlexJS] Status on Maven migration Forgot to ask... On 4/23/16, 2:06 AM, "Christofer Dutz" wrote: >Regarding the double run externc ... I noticed this too ... but I think I >managed to get everything working with just one pass in the Maven build. >In order to get things running I compared the output with the final >output of the Ant JavaScript and re-engineered ALL of the replacement >operations. So eventually looking at the replacements of the maven build >could eliminate the need to run externc twice. OK, I guess I will someday switch to using your replace tools. I've been wondering if there is some other way we should be doing this. Should we just use patch files instead? > >Regarding the merge ... I'm ready when you are. Are you also done with flex-asjs? I haven't looked there at all yet. -Alex
AW: AW: AW: AW: AW: [FlexJS] Status on Maven migration
No I'm still quite far from finished with that. I am coming closer and closer, but still I need to do some work. Currently the Core module is not building. Haven't had the time to dig into that though cause I was stuck with merging falcon stuff. One thing I did notice two days ago, was that I have to compile ASJS with the Flex Tool Group "FlexJS" (that's in falcon-jx) and the externs are compiled using the group "Falcon" (that's in falcon). I would have expected the externs to be compiled using the falcon-jx compiler as the externs belong to the cross compilation tool-chain ... any reason why they don't compile using falcon-jx? Chris Von: Alex Harui Gesendet: Samstag, 23. April 2016 18:10 An: dev@flex.apache.org Betreff: Re: AW: AW: AW: AW: [FlexJS] Status on Maven migration Forgot to ask... On 4/23/16, 2:06 AM, "Christofer Dutz" wrote: >Regarding the double run externc ... I noticed this too ... but I think I >managed to get everything working with just one pass in the Maven build. >In order to get things running I compared the output with the final >output of the Ant JavaScript and re-engineered ALL of the replacement >operations. So eventually looking at the replacements of the maven build >could eliminate the need to run externc twice. OK, I guess I will someday switch to using your replace tools. I've been wondering if there is some other way we should be doing this. Should we just use patch files instead? > >Regarding the merge ... I'm ready when you are. Are you also done with flex-asjs? I haven't looked there at all yet. -Alex
Re: AW: AW: AW: AW: [FlexJS] Status on Maven migration
Forgot to ask... On 4/23/16, 2:06 AM, "Christofer Dutz" wrote: >Regarding the double run externc ... I noticed this too ... but I think I >managed to get everything working with just one pass in the Maven build. >In order to get things running I compared the output with the final >output of the Ant JavaScript and re-engineered ALL of the replacement >operations. So eventually looking at the replacements of the maven build >could eliminate the need to run externc twice. OK, I guess I will someday switch to using your replace tools. I've been wondering if there is some other way we should be doing this. Should we just use patch files instead? > >Regarding the merge ... I'm ready when you are. Are you also done with flex-asjs? I haven't looked there at all yet. -Alex
Re: AW: AW: AW: AW: [FlexJS] Status on Maven migration
On 4/23/16, 2:06 AM, "Christofer Dutz" wrote: > >So you want/did add the source files of swfutils to the falcon projects? >in what branch did you do that? Can I now remove the dependency to the >Flex 4.15 SDK? The Ant script in maven-migration-test downloads certain source files. They are not checked in. Not sure how you want to adjust the Maven build. > >Regarding the merge ... I'm ready when you are. I want to verify the install of a nightly will work. Might take all weekend to get that far. -Alex
AW: AW: AW: AW: [FlexJS] Status on Maven migration
Aggregating responses to multiple mails: You couldn't find anything in Maven-central, cause we never released it as maven artifact. What I'm doing currently is simply mavenizing the 4.15 FDK and referencing the swfutils from there, but that dependency doesn't have any further dependencies, but that's just because I didn't model them in the mavenizer. Regarding the double run externc ... I noticed this too ... but I think I managed to get everything working with just one pass in the Maven build. In order to get things running I compared the output with the final output of the Ant JavaScript and re-engineered ALL of the replacement operations. So eventually looking at the replacements of the maven build could eliminate the need to run externc twice. So you want/did add the source files of swfutils to the falcon projects? in what branch did you do that? Can I now remove the dependency to the Flex 4.15 SDK? Regarding the merge ... I'm ready when you are. Chris Von: Alex Harui Gesendet: Freitag, 22. April 2016 18:35 An: dev@flex.apache.org Betreff: Re: AW: AW: AW: [FlexJS] Status on Maven migration On 4/22/16, 1:11 AM, "Christofer Dutz" 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 from there. Is that ok? Thanks, -Alex
