On Wed, Nov 28, 2012 at 5:49 AM, christofer.d...@c-ware.de < christofer.d...@c-ware.de> wrote:
> 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. > Just about as close to perfect as you could get. +1. Greg
