Hi Cosma, as Toni already confirmed, the mavenizer is currently the easiest way to create maven artifacts from a Flex SDK you downloaded using the Downloader. The Mavenizer doesn't actually require the Air SDK, the problem was, that the Mavenizer is able to mavenize any Flex SDK starting from Adobe Flex 2 up to 4.11. In order to be able to User newer Air versions with older FDKs I added the ability to mavenize the Air SDKs separately.
I think I remember creating all the runtime archives for any platform (Flashplayer or Air Runtime) found in the Flex SDK or the Air SDK. So if the SDK contains a "win" dir, it creates the windows archive, if lnx the ones for Linus and mac the ones for Macs. When deploying to your local maven repository, I would suggest to give my new deployer a testdrive. It should be noticeably faster with deploying the artifacts. (SDKInVMDeployer). Please don’t start that dreaded "deploy flex to a public repo"-thread ... the discussion always tends to explode in tons of emails and then suddenly ends nowhere, so I have given up on this. I think the FDK Downloader + Mavenizer path being the least complicated path. All others will definitely end in a support-mayhem because from my experience on the Flexmojos Mailinglist (when it still existed) was that people don't read documentation ;-) Chris -----Ursprüngliche Nachricht----- Von: Cosma Colanicchia [mailto:cosma...@gmail.com] Gesendet: Dienstag, 19. November 2013 18:26 An: Apache Flex Developers ML Betreff: Questions about current mavenizer status Hi there, I’m in the process of trying of rolling out Apache Flex 4.11 internally for the other employees of my company, and I need to deploy the related artifacts to the company Maven repo. AFAIK, the only way to do this for 4.11 is by mavenizing/deploying a downloaded FDK, is this right? I was following the other thread about storing ready-to-use artifacts in some public repository, but this path doesn’t seem ready yet (BTW, is there something I could do to help in this effort?) I managed to successfully build and mavenize the FDK from develop branch in some months ago, but I still have some questions: Q1 - I’m going to try running the mavenizer/deployer tools on the output of the Apache Flex Installer in order to mavenize the released 4.11 FDK, is this the intended way of using it? Q2 - the mavenizer requires the AIR runtime in a separate directory... but the installer output should already have integrated it in the FDK, should provide it separately anyway? Q3 - is the FDK produced by the installer cross-platform? This time I’m using a Mac to run the installer, so it has probably downloaded the Mac version of the AIR SDK.. does this mean that, when mavenizing this SDK, the Windows binaries (e.g. adt command line tool) won’t be included in the SDK artifacts and the SDK won’t be fully compatible with developers on Windows machines? Thank you for any help Cosma
