Well what you should do is download or install the FDK you want to mavenize.
I guess you have already done that. The mavenizer now takes this installation directory and untangles the Flex, Flash, Air stuff and generates Maven artifacts from that. So actually you should only have to run the Mavenizer pointing the directory containing your FDK and a target directory as output (I would not recommend to output the artifacts directly to "~userhome/.m2/repository" as I do like to check what the mavenizer did. As soon as you are satisfied with the results, simply copy the artifacts to your local Maven repo and/or deploy it to your Nexus/Artifactory/Whatsoever. I just added a page to the Apache Flex Wiki on how to use the Mavenizer: https://cwiki.apache.org/confluence/display/FLEX/Apache+Flex+SDK+Mavenizer Hope this explains stuff a little more. Chris Von: Humberto Sanchez II [mailto:[email protected]] Gesendet: Freitag, 3. Mai 2013 21:48 An: [email protected] Betreff: Mavenizing Flex SDKs Hello, I read through this: https://flexmojos.atlassian.net/wiki/display/FLEXMOJOS/Flexmojos+6.x And this: https://flexmojos.atlassian.net/wiki/display/FLEXMOJOS/Migrating+to+6.x I did get the mavenizer checked out, compiled and executable However, unclear to me how to get the Air and flex 4.9.x SDK into the format. The Flex SDK installer kinds of jams them together. Do I have to build the SDK from scratch? Or am I making this too hard and the 4.9.1 Flex SDKs are in a public maven repository already? Or am I just dense? Don't answer that. :-) Regards, Humberto [cid:61EFEC66-6342-4CB2-8566-583A2DA5155A] _________________________________________________
