Sounds perfect to me. I just have one question regarding the option for non-interactive builds: would that be acceptable for Adobe? In this case no one would explicitly accept the license and there's nothing that prohibits a "human" developer to use this property as well.
On Wed, Nov 28, 2012 at 12:49 PM, christofer.d...@c-ware.de < christofer.d...@c-ware.de> wrote: > No Offense taken ... after all .. I didn't write the tool, I simply took > over maintaining it and got the code back on track (Testsuite was failling > in more than 30 Tests). > > I think the maven pluigin would be automatically downloaded as is the case > with all other maven plugins, so I guess no manual step would have to be > done. > > What would you all think of the following solution: > - Apache deploys the Apache Flex FDK artifacts in a public maven repo > (Without the Apache stuff you need a license for) > - In the maven-flex-plugin suite there is one mojo that binds to mavens > "initialize" phase and checks the availability of the Apache artifacts. If > they are missing it prompts the user if he accepts the license agreement > (An option to allow a non-interactive build would be good for running on > CI-Servers) > - The Adobe-Stuff-Deployer mojo internally uses part of the Mavenizer to > deploy artifacts to the local maven repo. > - The rest of the maven-flex-plugin suite uses the atrifacts in the repo > as in any normal build. > > I think this solution should suite the needs of: > - Adobe, because people need to accept the licenses > - Developers, because they don't have to manually do more than accept a > license agreement by typing: "y". > - Coporates, because the generated artifacts could be deployed to local > Maven repos. > > Chris > > ________________________________________ > Von: Maxime Cowez [maxime.co...@gmail.com] > Gesendet: Mittwoch, 28. November 2012 12:24 > An: flex-dev@incubator.apache.org > Betreff: Re: [POLL] Maven and Apache Flex > > I am actually using Gradle with GradleFx plugin (sorry Chris, had too many > issues with FlexMojos :-/ ). Gradle uses Maven under the hood. My answers > to the first 5 questions should be interpreted from that angle. > > > > 1. Number of people who will use Maven to develop Flex apps at your > company > > (0 if you have no interest in using Maven). > > > > 1 (I'm the only Flex dev) > 9, if you count the java devs that need my build scripts to build their web > apps > > > > 2. Maven would be used to develop apps for FlashPlayer in the browser > (yes > > or no) > > > > yes > > > > > > 3. Maven would be used to develop apps for AIR on desktop/laptops (yes or > > no) > > > > no (not yet, but possibly in the future) > > > > 4. Maven would be used to develop apps for AIR on Android (yes or no) > > > > no (not yet, but possibly in the future) > > > > > > 5. Maven would be used to develop apps for AIR on IOS (yes or no) > > > > no (not yet, but possibly in the future) > > > > > > 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 > > > > 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. > > > > 0 (see remarks below) > > > > 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. > > > > 0 (see remarks below) > > > > 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 > > > > 0 > > > > 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. > > > > 0 > > Remarks: > - The number of steps to be taken by a Java developer that needs to compile > my Flex apps should be 0 (accepting a license would be acceptable). > - I haven't given a positive number to any of the proposed implementations, > because all of them require at least one manual step, which violates my > previous requirement. Unless I didn't understand them correctly; if > downloading the Maven plugin is part of the build process, then my answer > should be "2" for those solutions. Otherwise downloading the Maven plugin > manually would be closest to acceptable because I assume it comes closest > to what the java devs are already used to do. > - For reference, this is how it is handled in GradleFx: > - the GradleFx plugin is downloaded and cached automatically by Gradle > - the Flex SDK is downloaded and cached automatically by > Gradle/GradleFx, including Adobe's proprietary libraries; the licenses must > be accepted once > - other dependencies are downloaded and cached, and the application is > built > - the Java devs don't even have to install Gradle because I commit the > Flex app with a so-called Gradle "wrapper", a lightweight standalone build > tool. Unfortunately this feature is specific to Gradle and doesn't exist in > Maven (as far as I know). > > > > > Thanks in advance. Remember that polls are not binding, but your input > is > > much appreciated. > > > > -- > > Alex Harui > > Flex SDK Team > > Adobe Systems, Inc. > > http://blogs.adobe.com/aharui > > > > >
