I'm just using Aether for deploying mavenized FDKs so it has nothing to do with the actual execution of FM. So there shouldn't be a Problem.
Chris ________________________________________ Von: Frédéric THOMAS [webdoubl...@hotmail.com] Gesendet: Dienstag, 5. November 2013 00:38 An: dev@flex.apache.org Betreff: RE: Updated Mavenizer Thanks Chris, sounds good, I don't have the time at the moment to look at the code because of my work and I'm between Paris and London but will check it as soon as I can, just a question, are you aware there is an issue with FM and Aether running FM with maven 3.1.1 ? Should I raise an issue somewhere ? -Fred -----Message d'origine----- De : christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de] Envoyé : dimanche 3 novembre 2013 16:00 À : dev@flex.apache.org Objet : Updated Mavenizer Hi, today I committed some changes to the Mavenizer Tool. Change 1 made sure all SDKs (Flex and Air) are processed in the right order regarding the versions of the SDKs. Change 2 is a new Deployer "SDKInVMDeployer" which no longer needs Maven to deploy the Mavenized files as it uses Aether directly to deploy files directly inside the VM, causing a dramatic speedup of the time needed to deploy stuff as well as being able to execute without the reliance on an already installed Maven system. This should make it easy to add the new Deployer to any sort of installer. Chris
