On 11/14/12 2:11 AM, "christofer.d...@c-ware.de" <christofer.d...@c-ware.de>
wrote:
>
> There were things, that were really annoying:
> - No Flex FDKs in public Maven repos due to licensing stuff (Even if the
> player stuff still needs to be referenced ... @Alex ... you mentioned some
> internal discussions at Adobe about this ... any changes you'd like to share?)
I got a lot of warm fuzzies in my meeting. The killer issue seems to be
that the AIR SDK actually contains the AIR runtime for the "captive runtime"
feature. Legal says they are going to ponder if there are licenses that
still protect not just Adobe, but the closed-source third-party code in the
runtimes, but they are doubtful. I also have a query out about whether the
runtimes in the AIR SDK are true executables or more like libraries for the
packager, which could give us some wiggle room.
Anyway, I think the answer is going to be that the runtimes can't be
downloaded directly by Maven.
I suppose one could argue that many Maven users don't need the AIR SDK or at
least, the runtimes in the AIR SDK if they aren't building mobile apps with
Maven. We could take that angle if that's really true and try to get a
subset of the AIR SDK under Maven.
But my research indicates that in general, Maven users download other
proprietary stuff and host it in their own private Maven repos, so the
Mavenizers in Apache could certainly help take downloaded AIR SDKs and
PlayerGlobal and deploy to private Maven repos.
I'll let you know if I hear otherwise.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
