Re: AW: AW: AW: AW: [FALCONJX] Some help with the externs
On 3/23/16, 1:24 AM, "Christofer Dutz" wrote: >Ok think I found the problem ... > >I had to update flex-asjs after that's done, I get: > >BUILD SUCCESSFUL >Total time: 2 minutes 21 seconds > >I don't think it's a good Idea to depend on flex-asjs to build falcon, >but I think I stated that earlier. >But it doesn't explain why I can't find the reason for reporting errors >in the log. Or am I just to Ant-blind? At one point in time, the ant script for the test folders had a default target that ran the subset of tests that didn't have flex-asjs dependencies. I just got through testing the falconjx source package and I think it worked that way. But for sure, there are tests in there that have flex-asjs dependencies, but they should be hooked to a different Ant target (ant all). -Alex
AW: AW: AW: AW: [FALCONJX] Some help with the externs
Ok think I found the problem ... I had to update flex-asjs after that's done, I get: BUILD SUCCESSFUL Total time: 2 minutes 21 seconds I don't think it's a good Idea to depend on flex-asjs to build falcon, but I think I stated that earlier. But it doesn't explain why I can't find the reason for reporting errors in the log. Or am I just to Ant-blind? Chris Von: Christofer Dutz Gesendet: Mittwoch, 23. März 2016 09:18 An: dev@flex.apache.org Betreff: AW: AW: AW: AW: [FALCONJX] Some help with the externs Hi Alex, Well Here is the complete log of that build ... I did a wipe-all before the build and then an "ant all" I can't see real errors ... the only ones come from externc and I was told they can be ignored, but in any case the log reports two times 4 errors, but that would sum up to 8 for me and not 14 :-( https://paste.apache.org/Lmfa Chris Von: Alex Harui Gesendet: Mittwoch, 23. März 2016 05:33 An: dev@flex.apache.org Betreff: Re: AW: AW: AW: [FALCONJX] Some help with the externs Not sure. Can you tell if it is old tests from compiler.tests or compiler.jx.tests? What is in the console before the failure report? -Alex On 3/22/16, 3:10 PM, "Christofer Dutz" wrote: >Sorry for that ... I noticed the Ignore right after posting the email. >But I added a new constant to the jquery extern and updated the test, and >it now seems to pass. > >I did some more streamlining of tests and just wanted to ask ... I think >I remember 14 errors in the end before my changes, and now I still have >14 errors ... I couldn't find any failing tests and 2 x 4 errors in the >generation of JavaScript (which seems to be ok). Does anyone know where >the 14 errors the build is reporting come from? > >Chris > > >Von: Michael Schmalle >Gesendet: Dienstag, 22. März 2016 20:56 >An: dev@flex.apache.org >Betreff: Re: AW: AW: [FALCONJX] Some help with the externs > >Yeah and when I wrote the test, the externs were in a different place that >I was testing. I think Alex or somebody else refactored the locations, and >if it does have an @Ignore, that would backup the fact the test wasn't run >since that refactor. > >Mike > >On Tue, Mar 22, 2016 at 3:46 PM, Alex Harui wrote: > >> I think that test has a @ignore on the entire test class. >> >> -Alex >> >> On 3/22/16, 12:32 PM, "Christofer Dutz" >>wrote: >> >> >Another thing I just noticed while separating the tests that I need to >> >adjust from the ones I need to move: >> >Ho can the test TestExternJQuery pass? In the configure it creates a >>path: >> >String coreRoot = >> >ExternalsTestUtils.EXTERNAL_JS_DIR.getAbsolutePath(); >> >config.addExternal(coreRoot + "/jquery-1.9.js"); >> > >> >The stupid thing is this evaluates to >> >"../externs/js/externs/jquery-1.9.js" but this file does not exist as >>it >> >should be "../externs/jquery/externs/jquery-1.9.js" ... so I would like >> >to state that I mistrust this test ;-) >> > >> >Chris >> > >> > >> >Von: carlos.rov...@gmail.com im Auftrag von >> >Carlos Rovira >> >Gesendet: Sonntag, 20. März 2016 09:29 >> >An: dev@flex.apache.org >> >Betreff: Re: AW: [FALCONJX] Some help with the externs >> > >> >Amazing work Chris! Thanks to share your progress! :) >> > >> >2016-03-19 14:33 GMT+01:00 Christofer Dutz : >> > >> >> YE! >> >> >> >> I finally managed to port the builds for ALL externs to maven. I was >> >> thinking about how I could de-couple the compiler and the maven >>plugin >> >>till >> >> I noticed that this was exactly the problem I always had with >>Flexmojos >> >>and >> >> what I created the Flex tool-api for. With this it was super easy to >> >>create >> >> universal Maven plugins for externc and mxmlc. >> >> >> >> Currently the maven build is far from perfect ... currently I >>reference >> >> the js.swc via relative paths, which is a super no-go for production, >> >>but >> >> at least I can build and as Ant used relative paths it's not even a >>step >> >> back :-) >> >> >> >> Also every module is currently still a "jar" project and hence maven >> >> produces "jar" files in the target, all of which a
AW: AW: AW: AW: [FALCONJX] Some help with the externs
Hi Alex, Well Here is the complete log of that build ... I did a wipe-all before the build and then an "ant all" I can't see real errors ... the only ones come from externc and I was told they can be ignored, but in any case the log reports two times 4 errors, but that would sum up to 8 for me and not 14 :-( https://paste.apache.org/Lmfa Chris Von: Alex Harui Gesendet: Mittwoch, 23. März 2016 05:33 An: dev@flex.apache.org Betreff: Re: AW: AW: AW: [FALCONJX] Some help with the externs Not sure. Can you tell if it is old tests from compiler.tests or compiler.jx.tests? What is in the console before the failure report? -Alex On 3/22/16, 3:10 PM, "Christofer Dutz" wrote: >Sorry for that ... I noticed the Ignore right after posting the email. >But I added a new constant to the jquery extern and updated the test, and >it now seems to pass. > >I did some more streamlining of tests and just wanted to ask ... I think >I remember 14 errors in the end before my changes, and now I still have >14 errors ... I couldn't find any failing tests and 2 x 4 errors in the >generation of JavaScript (which seems to be ok). Does anyone know where >the 14 errors the build is reporting come from? > >Chris > > >Von: Michael Schmalle >Gesendet: Dienstag, 22. März 2016 20:56 >An: dev@flex.apache.org >Betreff: Re: AW: AW: [FALCONJX] Some help with the externs > >Yeah and when I wrote the test, the externs were in a different place that >I was testing. I think Alex or somebody else refactored the locations, and >if it does have an @Ignore, that would backup the fact the test wasn't run >since that refactor. > >Mike > >On Tue, Mar 22, 2016 at 3:46 PM, Alex Harui wrote: > >> I think that test has a @ignore on the entire test class. >> >> -Alex >> >> On 3/22/16, 12:32 PM, "Christofer Dutz" >>wrote: >> >> >Another thing I just noticed while separating the tests that I need to >> >adjust from the ones I need to move: >> >Ho can the test TestExternJQuery pass? In the configure it creates a >>path: >> >String coreRoot = >> >ExternalsTestUtils.EXTERNAL_JS_DIR.getAbsolutePath(); >> >config.addExternal(coreRoot + "/jquery-1.9.js"); >> > >> >The stupid thing is this evaluates to >> >"../externs/js/externs/jquery-1.9.js" but this file does not exist as >>it >> >should be "../externs/jquery/externs/jquery-1.9.js" ... so I would like >> >to state that I mistrust this test ;-) >> > >> >Chris >> > >> > >> >Von: carlos.rov...@gmail.com im Auftrag von >> >Carlos Rovira >> >Gesendet: Sonntag, 20. März 2016 09:29 >> >An: dev@flex.apache.org >> >Betreff: Re: AW: [FALCONJX] Some help with the externs >> > >> >Amazing work Chris! Thanks to share your progress! :) >> > >> >2016-03-19 14:33 GMT+01:00 Christofer Dutz : >> > >> >> YE! >> >> >> >> I finally managed to port the builds for ALL externs to maven. I was >> >> thinking about how I could de-couple the compiler and the maven >>plugin >> >>till >> >> I noticed that this was exactly the problem I always had with >>Flexmojos >> >>and >> >> what I created the Flex tool-api for. With this it was super easy to >> >>create >> >> universal Maven plugins for externc and mxmlc. >> >> >> >> Currently the maven build is far from perfect ... currently I >>reference >> >> the js.swc via relative paths, which is a super no-go for production, >> >>but >> >> at least I can build and as Ant used relative paths it's not even a >>step >> >> back :-) >> >> >> >> Also every module is currently still a "jar" project and hence maven >> >> produces "jar" files in the target, all of which are probably >>completely >> >> empty. In order to address this I will actually have to provide a >>custom >> >> lifecycle mapping which will make the hack more and more real flex >> >>support >> >> for maven. >> >> >> >> Now I have to find out how to separate the tests that currently use >> >>other >> >> parts of the build and move them into a dedicated "testsuite" module. >> >> >> >> But I think for now the hardest steps have been taken
Re: AW: AW: AW: [FALCONJX] Some help with the externs
Not sure. Can you tell if it is old tests from compiler.tests or compiler.jx.tests? What is in the console before the failure report? -Alex On 3/22/16, 3:10 PM, "Christofer Dutz" wrote: >Sorry for that ... I noticed the Ignore right after posting the email. >But I added a new constant to the jquery extern and updated the test, and >it now seems to pass. > >I did some more streamlining of tests and just wanted to ask ... I think >I remember 14 errors in the end before my changes, and now I still have >14 errors ... I couldn't find any failing tests and 2 x 4 errors in the >generation of JavaScript (which seems to be ok). Does anyone know where >the 14 errors the build is reporting come from? > >Chris > > >Von: Michael Schmalle >Gesendet: Dienstag, 22. März 2016 20:56 >An: dev@flex.apache.org >Betreff: Re: AW: AW: [FALCONJX] Some help with the externs > >Yeah and when I wrote the test, the externs were in a different place that >I was testing. I think Alex or somebody else refactored the locations, and >if it does have an @Ignore, that would backup the fact the test wasn't run >since that refactor. > >Mike > >On Tue, Mar 22, 2016 at 3:46 PM, Alex Harui wrote: > >> I think that test has a @ignore on the entire test class. >> >> -Alex >> >> On 3/22/16, 12:32 PM, "Christofer Dutz" >>wrote: >> >> >Another thing I just noticed while separating the tests that I need to >> >adjust from the ones I need to move: >> >Ho can the test TestExternJQuery pass? In the configure it creates a >>path: >> >String coreRoot = >> >ExternalsTestUtils.EXTERNAL_JS_DIR.getAbsolutePath(); >> >config.addExternal(coreRoot + "/jquery-1.9.js"); >> > >> >The stupid thing is this evaluates to >> >"../externs/js/externs/jquery-1.9.js" but this file does not exist as >>it >> >should be "../externs/jquery/externs/jquery-1.9.js" ... so I would like >> >to state that I mistrust this test ;-) >> > >> >Chris >> > >> > >> >Von: carlos.rov...@gmail.com im Auftrag von >> >Carlos Rovira >> >Gesendet: Sonntag, 20. März 2016 09:29 >> >An: dev@flex.apache.org >> >Betreff: Re: AW: [FALCONJX] Some help with the externs >> > >> >Amazing work Chris! Thanks to share your progress! :) >> > >> >2016-03-19 14:33 GMT+01:00 Christofer Dutz : >> > >> >> YE! >> >> >> >> I finally managed to port the builds for ALL externs to maven. I was >> >> thinking about how I could de-couple the compiler and the maven >>plugin >> >>till >> >> I noticed that this was exactly the problem I always had with >>Flexmojos >> >>and >> >> what I created the Flex tool-api for. With this it was super easy to >> >>create >> >> universal Maven plugins for externc and mxmlc. >> >> >> >> Currently the maven build is far from perfect ... currently I >>reference >> >> the js.swc via relative paths, which is a super no-go for production, >> >>but >> >> at least I can build and as Ant used relative paths it's not even a >>step >> >> back :-) >> >> >> >> Also every module is currently still a "jar" project and hence maven >> >> produces "jar" files in the target, all of which are probably >>completely >> >> empty. In order to address this I will actually have to provide a >>custom >> >> lifecycle mapping which will make the hack more and more real flex >> >>support >> >> for maven. >> >> >> >> Now I have to find out how to separate the tests that currently use >> >>other >> >> parts of the build and move them into a dedicated "testsuite" module. >> >> >> >> But I think for now the hardest steps have been taken. >> >> >> >> Now I'm going to actually start programming my Cyborg ... don't want >>to >> >> arrive at ApacheCon with nothing to show ;-) >> >> >> >> Chris >> >> >> >> >> >> Von: Christofer Dutz >> >> Gesendet: Samstag, 19. März 2016 11:02 >> >> An: dev@flex.apache.org >> >> Betreff: AW: AW: [FALCONJX] Some help with the externs >> >> >> >> Ok ... so have a look at this image :-) >> >> >> >> >> >>http://s21.postimg.org/lx4dux0jr/Bildschirmfoto_2016_03_19_um_10_53_31.pn >> >>g >> >> >> >> I finally managed to finish a first build of an extern swc, using >>Maven >> >> and using my brand-new externc and compiler Maven plugins. My plugins >> >>are >> >> currently a simple prototype wich I am hoping to extend to support >> >> everything needed to build the test cases in the test suite. As the >> >>rest of >> >> the compiler blows up if you leave the 100% correct path at least I >> >>have no >> >> pressure to make it perfect ... so I'll stick to "it doesn't blow up >>if >> >>you >> >> do everything correct"-strategy for now, which makes things a lot >> >>simpler >> >> (but also unusable for others) >> >> >> >> Currently my plugins are tightly coupled with compiler and >>compiler.jx >> >>... >> >> this would complicate the build, so I think I'm going to use my >> >>Tool-API to >> >> decouple them. And I am going to write the plugin in the falco
AW: AW: AW: [FALCONJX] Some help with the externs
Sorry for that ... I noticed the Ignore right after posting the email. But I added a new constant to the jquery extern and updated the test, and it now seems to pass. I did some more streamlining of tests and just wanted to ask ... I think I remember 14 errors in the end before my changes, and now I still have 14 errors ... I couldn't find any failing tests and 2 x 4 errors in the generation of JavaScript (which seems to be ok). Does anyone know where the 14 errors the build is reporting come from? Chris Von: Michael Schmalle Gesendet: Dienstag, 22. März 2016 20:56 An: dev@flex.apache.org Betreff: Re: AW: AW: [FALCONJX] Some help with the externs Yeah and when I wrote the test, the externs were in a different place that I was testing. I think Alex or somebody else refactored the locations, and if it does have an @Ignore, that would backup the fact the test wasn't run since that refactor. Mike On Tue, Mar 22, 2016 at 3:46 PM, Alex Harui wrote: > I think that test has a @ignore on the entire test class. > > -Alex > > On 3/22/16, 12:32 PM, "Christofer Dutz" wrote: > > >Another thing I just noticed while separating the tests that I need to > >adjust from the ones I need to move: > >Ho can the test TestExternJQuery pass? In the configure it creates a path: > >String coreRoot = > >ExternalsTestUtils.EXTERNAL_JS_DIR.getAbsolutePath(); > >config.addExternal(coreRoot + "/jquery-1.9.js"); > > > >The stupid thing is this evaluates to > >"../externs/js/externs/jquery-1.9.js" but this file does not exist as it > >should be "../externs/jquery/externs/jquery-1.9.js" ... so I would like > >to state that I mistrust this test ;-) > > > >Chris > > > > > >Von: carlos.rov...@gmail.com im Auftrag von > >Carlos Rovira > >Gesendet: Sonntag, 20. März 2016 09:29 > >An: dev@flex.apache.org > >Betreff: Re: AW: [FALCONJX] Some help with the externs > > > >Amazing work Chris! Thanks to share your progress! :) > > > >2016-03-19 14:33 GMT+01:00 Christofer Dutz : > > > >> YE! > >> > >> I finally managed to port the builds for ALL externs to maven. I was > >> thinking about how I could de-couple the compiler and the maven plugin > >>till > >> I noticed that this was exactly the problem I always had with Flexmojos > >>and > >> what I created the Flex tool-api for. With this it was super easy to > >>create > >> universal Maven plugins for externc and mxmlc. > >> > >> Currently the maven build is far from perfect ... currently I reference > >> the js.swc via relative paths, which is a super no-go for production, > >>but > >> at least I can build and as Ant used relative paths it's not even a step > >> back :-) > >> > >> Also every module is currently still a "jar" project and hence maven > >> produces "jar" files in the target, all of which are probably completely > >> empty. In order to address this I will actually have to provide a custom > >> lifecycle mapping which will make the hack more and more real flex > >>support > >> for maven. > >> > >> Now I have to find out how to separate the tests that currently use > >>other > >> parts of the build and move them into a dedicated "testsuite" module. > >> > >> But I think for now the hardest steps have been taken. > >> > >> Now I'm going to actually start programming my Cyborg ... don't want to > >> arrive at ApacheCon with nothing to show ;-) > >> > >> Chris > >> > >> > >> Von: Christofer Dutz > >> Gesendet: Samstag, 19. März 2016 11:02 > >> An: dev@flex.apache.org > >> Betreff: AW: AW: [FALCONJX] Some help with the externs > >> > >> Ok ... so have a look at this image :-) > >> > >> > http://s21.postimg.org/lx4dux0jr/Bildschirmfoto_2016_03_19_um_10_53_31.pn > >>g > >> > >> I finally managed to finish a first build of an extern swc, using Maven > >> and using my brand-new externc and compiler Maven plugins. My plugins > >>are > >> currently a simple prototype wich I am hoping to extend to support > >> everything needed to build the test cases in the test suite. As the > >>rest of > >> the compiler blows up if you leave the 100% correct path at least I > >>have no > >> pressure to make it perfect ... so I'll stick to "it doesn't blow up if > >>you > >> do everything correct"-strategy for now, which makes things a lot > >>simpler > >> (but also unusable for others) > >> > >> Currently my plugins are tightly coupled with compiler and compiler.jx > >>... > >> this would complicate the build, so I think I'm going to use my > >>Tool-API to > >> decouple them. And I am going to write the plugin in the falcon repo as > >>it > >> makes things very complicated as long as not everything is released at > >> least once. > >> > >> Chris > >> > >> > >> Von: Christofer Dutz > >> Gesendet: Samstag, 19. März 2016 09:19 > >> An: dev@flex.apache.org > >> Betreff: AW: AW: [FALCONJX] Some help with the externs >
