Hi, > From the Installer, users already have to accept licenses for the third > party artifacts, for those users I can grant access to a online maven repo > which serves the Mavenized SDKs What to stop users sharing that URL and/or user credentials around?
> I can even add the lasts nightly mavenized build versions. As long as you make it clear that these are not official releases and for development use only as per Apache policy. > The server exist today as it serves me, it serves up to the 4.11 version Could it cope with it load and the costs that is likely to incur (assume 100 or 200 installs a day)? Who owns and maintains the server? Could the apache Flex PMC be given access to it? Thanks, Justin
