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 :-) 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 :-) Chris ________________________________________ Von: Alex Harui <aha...@adobe.com> Gesendet: Mittwoch, 24. Februar 2016 17:04 An: dev@flex.apache.org Betreff: Re: [FALCON] Compiling Falcon with Maven On 2/24/16, 4:19 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >Hi, > >so I managed to get all Unit-Tests to pass: >"Tests run: 375, Failures: 0, Errors: 0, Skipped: 26" Yay! >currently having a little trouble with the resource-bundles as I'm >getting a lot of: >"Error: Unable to resolve resource bundle 'messaging'" >For a lot of other bundles too ... > >I don't quite know why, but I'll dig into that later on ... That might be that you are not using en_US and the SDK in flex-sdk hasn't been built with the other-locales target (to produce de_DE for you). -Alex
