Le 27/11/2012 19:46, Alex Harui a écrit : > 1. Number of people who will use Maven to develop Flex apps at your company > (0 if you have no interest in using Maven). 5-10 (Small agency, we're using maven to build /every/ Flash/Flex based project since Flex 3).
> 2. Maven would be used to develop apps for FlashPlayer in the browser (yes > or no) yes (currently used) > 3. Maven would be used to develop apps for AIR on desktop/laptops (yes or > no) yes (currently used) > 4. Maven would be used to develop apps for AIR on Android (yes or no) yes (currently used, with home made scripts for the final apk packaging) > 5. Maven would be used to develop apps for AIR on IOS (yes or no) yes (currently used, with home made scripts for the final apk packaging) > 6. Rate the following proposed implementations (-1 = not acceptable, 0 = > neutral, 1 = acceptable, 2 = preferred) > a) You must manually download the Player SDK and AIR SDK from the Adobe > site and set up environment variables pointing to them -1 : the whole point of using maven project descriptor is to streamline project builds would it be on the developper station, the integration server or the release process. Dependent artifacts have to be 'mavenized' and available on a shared repo (private or public). > b) You must download and install a Maven plug-in from the Apache Flex > site. The first time you use Maven on a computer, it will ask you > to accept the Adobe license agreement. 2 > c) You must download and install a Maven plug-in from the Adobe > site. The first time you use Maven on a computer, it will ask you > to accept the Adobe license agreement. 1 Aactually, it's more to be sure that every artifact needed for a given Flex version will be gathered a the same place instead of living on several repositories, leading to potential issues. But if versioning of playerglobal/air sdk is completely independant of flex versioning AND if the compatiblity matrix between each others can be expressed in form of maven dependency graph, it wouldn't be an issue to ship some artifact from Adobe's repo and others from Apache's repo. > d) Maven can be used as-is for FlashPlayer apps and AIR apps on > desktops/laptops, but not for AIR apps on Android/IOS. To target > Android/IOS, you must use one of the first three implementations 2, this is currently the case with Velo's mavenized SDK (prior SDK "Apachization") > e) We will manually download the Player SDKs and AIR SDKs and put them > in our local/private Maven repo. 0 > f) We would use a utility application that would download the Player > SDKs and AIR SDKs (prompting you to accept the license) and put them > in our local/private Maven repo. 1 (actually, "e" is implemented by Christopher's toolset but an "official" and maintained tool would be preferable). b & c : I think there's a confusion between the maven plugin that would be required to actually build something with mxmlc API and the SDK dependency artifact. There should no be licensing issue with the plugin itself but with the SDK artifact (AIR & playerglobal) only. And it'll be prompted for a license approval each time you use a SDK version for the first time. -- Simon
