AW: AW: [FALCON] Compiling Falcon with Maven

[Christofer Dutz <ch...@c-ware.de>]

Ok ... so I had some time to continue on the Maven-thing.
for now I updated the Maven build to use the FLASHPLAYER_DEBUGGER environment variable. 
With this I am now down to 0 Errors in the Unit-Tests and 32 Errors in the Integration tests. The integration tests errors seem to be related to paths being assembled based upon the old environment variables form the Ant built ... I think I should manage to minimize these problems ... fingers crossed.

Chris

________________________________________
Von: Alex Harui <ah...@adobe.com>
Gesendet: Mittwoch, 24. Februar 2016 17:24
An: dev@flex.apache.org
Betreff: Re: AW: [FALCON] Compiling Falcon with Maven

On 2/24/16, 8:15 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:

>Well I am using my mavenized sdks my sdk-converter provides me ... and I
>have all of these resource bundles available.
>
>Anyway ... I just finished releasing a new version of JBurg, that no
>longer has the classloader issues the 1.10.2 version had (JBurg 1.10.2
>used the system classloader to load stuff, in maven we have a fine
>hierarchy of classloaders, so changing this to the current threads
>context classloader resolved all issues I had). Paralel to that I did a
>first release of the jburg-maven-plugin (version 1.10.3 to match that of
>jburg). I also updated the versions in my branch. So you should be able
>to get the same results as I am having ... Well not quite ... thinking
>about it ... I still have the debug-player path hard coded :-(
>
>But I'm currently writing a simple DMG file decoder to read the
>debug-player dmg images. With that I'll be able to finish the
>sdk-converter to package the runtimes. As soon as that's done I can
>change the tests to auto-download the runtimes and as soon as you update
>the flash.version property, it will automatically run the correct player
>version :-)

I am trying to make sure this is ok with Adobe.  There are currently some
concerns.

>
>It finally feels like I'm getting somewhere :-)
>
>Now I have to convince you how awesome Maven is ... well I hope it will
>do the convincing on it's own :-)

This process of incremental changes and incremental education is what
works best for me.  I don't have to block out whole days to try to learn
something that won't stick in my head.  I can learn stuff as needed.  I
still don't have time and money budgeted for a full-day training on Maven
at ApacheCon.  I don't know if other folks who might go to ApacheCon have
the budget for it either.

I'm sure Maven is awesome, but if I can use it more as a black box, it is
better for me right now.

-Alex

AW: AW: [FALCON] Compiling Falcon with Maven

[Christofer Dutz <ch...@c-ware.de>]

Ok ... further investigation made me realize, that it's actually just the SDKSWCTests that's failing. 
This test tries to compile the individual projects of the original Flex SDK using falcon. 

I do understand that this might be a good test, but it does create quite a big dependency. I think it would be a good idea to move that into a separate integration test-module. 

Besides this one test, now all tests are green :-)
It turned out that the problem with the resource-bundles was related to the unit-tests being hard-coded to include the en_US resource bundles. My system is set to "de_DE" so the compiler wanted to find de_DE resources. I added a local argument to the argline to force it to use en_US on every system. Not it works. I think this also fixes my problems I had with failling tests in the Ant build that you (Alex) couldn't reproduce :-)

Chris



________________________________________
Von: Christofer Dutz <ch...@c-ware.de>
Gesendet: Dienstag, 8. März 2016 13:59
An: dev@flex.apache.org
Betreff: AW: AW: [FALCON] Compiling Falcon with Maven

Ok ... so I had some time to continue on the Maven-thing.
for now I updated the Maven build to use the FLASHPLAYER_DEBUGGER environment variable.
With this I am now down to 0 Errors in the Unit-Tests and 32 Errors in the Integration tests. The integration tests errors seem to be related to paths being assembled based upon the old environment variables form the Ant built ... I think I should manage to minimize these problems ... fingers crossed.

Chris

________________________________________
Von: Alex Harui <ah...@adobe.com>
Gesendet: Mittwoch, 24. Februar 2016 17:24
An: dev@flex.apache.org
Betreff: Re: AW: [FALCON] Compiling Falcon with Maven

On 2/24/16, 8:15 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:

>Well I am using my mavenized sdks my sdk-converter provides me ... and I
>have all of these resource bundles available.
>
>Anyway ... I just finished releasing a new version of JBurg, that no
>longer has the classloader issues the 1.10.2 version had (JBurg 1.10.2
>used the system classloader to load stuff, in maven we have a fine
>hierarchy of classloaders, so changing this to the current threads
>context classloader resolved all issues I had). Paralel to that I did a
>first release of the jburg-maven-plugin (version 1.10.3 to match that of
>jburg). I also updated the versions in my branch. So you should be able
>to get the same results as I am having ... Well not quite ... thinking
>about it ... I still have the debug-player path hard coded :-(
>
>But I'm currently writing a simple DMG file decoder to read the
>debug-player dmg images. With that I'll be able to finish the
>sdk-converter to package the runtimes. As soon as that's done I can
>change the tests to auto-download the runtimes and as soon as you update
>the flash.version property, it will automatically run the correct player
>version :-)

I am trying to make sure this is ok with Adobe.  There are currently some
concerns.

>
>It finally feels like I'm getting somewhere :-)
>
>Now I have to convince you how awesome Maven is ... well I hope it will
>do the convincing on it's own :-)

This process of incremental changes and incremental education is what
works best for me.  I don't have to block out whole days to try to learn
something that won't stick in my head.  I can learn stuff as needed.  I
still don't have time and money budgeted for a full-day training on Maven
at ApacheCon.  I don't know if other folks who might go to ApacheCon have
the budget for it either.

I'm sure Maven is awesome, but if I can use it more as a black box, it is
better for me right now.

-Alex