Thanks Chris, that's fine to me, even with the adobe groupId, was just enough you to confirm it, I'll re-run the mavenizer / deployer between today and tomorrow with all the existing SDKs on my new computer / artifactory and check if everything goes well, I will check it still possible to get a snapshot version from the develop branch too as I did before.
-Fred -----Message d'origine----- De : christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de] Envoyé : lundi 2 septembre 2013 16:40 À : dev@flex.apache.org Objet : AW: Problems running Mavenizer Hi, it's still that way ... and it's nothing I will be able to come upt with a fix though. The only Option would be to release Flexmojos in two flavours ... one that works with the Apache GID and one with the Adobe GID :-( Unfortunately as soon as I Switch to Apache GIDs the Testsuite completely Fails to run. This is the reason for me not having done this step yet). This is a issue releated to Maven and how you can override Default-Dependencies by providing a custom version, but not if the imported dependency has a different GID, then Maven will try to load dependencies with both GIDs and different Versions. So whenever you would use Flexmojos with an Apache FDK it would have the Default Adobe Flex dependencies it was compiled with pluss the ones from Apache which causes millions of Trouble. Sorry for not having a nicer answer ... But I guess it would be a good Idea do do such an 6.0.1-apache release to allow us to use our cool Apache FDKs without having to Name them Adobe ;-) Chris ________________________________________ Von: Frédéric THOMAS [webdoubl...@hotmail.com] Gesendet: Montag, 2. September 2013 12:40 An: dev@flex.apache.org Betreff: RE: Problems running Mavenizer Back to one year ago, the last time I used the apache groupId, I couldn't use the FDKs, I'm not sure to remember why but I guess that was because FM still use a compiler ref linked to the adobe groupId, so, I would pass always false to this parameter but maybe @Chris could remind us if it is still like that or not. Out of that, if you don't mind, I would like to implement that feature in the installer, sure I would need some help to make it working on mac and Linux (I'm thinking about the git detection), however, I've got already the code working for the windows part. > The README needs to be updated to reflect the fact that a third > parameter is required: "use-apache-gid" Yep, still need to install the SDK on my new computer, given today seems to be quiet, I guess I can handle that. -Fred -----Message d'origine----- De : omup...@gmail.com [mailto:omup...@gmail.com] De la part de OmPrakash Muppirala Envoyé : lundi 2 septembre 2013 09:58 À : dev@flex.apache.org Objet : Problems running Mavenizer I am following the README from here: https://fisheye6.atlassian.com/browse/flex-utilities/mavenizer/README.txt?hb =true A couple of problems: 1. The README needs to be updated to reflect the fact that a third parameter is required: "use-apache-gid" 2. When I run it in this format: C:\p\flex_os\workspace\flexroot\git\flex-utilities\mavenizer>java -cp target\flex-sdk-converter-1.0.jar SDKGenerator "C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6\sdks\ApacheFlex4.10.0" "C:\temp\mavenized" true or C:\p\flex_os\workspace\flexroot\git\flex-utilities\mavenizer>java -cp target\flex-sdk-converter-1.0.jar SDKGenerator "C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6\sdks\ApacheFlex4.10.0" "C:\temp\mavenized" false nothing seems to happen. No error message, no mavenized SDK, it just quits silently. I even tried copying the Apache Flex SDK to a directory with no spaces, still no luck. Before I dig in too much, any idea what could be going on here? Thanks, Om
