incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Conrad <>
Subject Re: Automatically downloading playerglobal, airglobal, Pixel Bender, Debug Player -- What constitutes explicitly choosing in non-default build option in a build script?
Date Thu, 16 Aug 2012 05:54:05 GMT
On Thu, Aug 16, 2012 at 1:17 AM, Alex Harui <> wrote:
> On 8/15/12 2:55 PM, "Jeff Conrad" <> wrote:
>> Question(s):
>> If we add prompts to download these items for the user, can we have
>> the prompt itself default to a 'yes' for a category X licensed item
>> like player/air global, Pixel Bender, or the Standalone Debug Flash
>> Player or does that violate the part about allowing the user to
>> explicitly choose?
> After Bertrand's email there was another thread where we got a "ruling" that
> playerglobal.swc was a "prerequisite".  That is because it isn't an option.
> Nothing will compile without it.  It represents the platform, and none of
> its binary information goes into the SWF.

I wonder what the difference between a "prerequisite" and a "system
requirement" is (if any)?

Per the 3rd party licensing page:

YOU MAY ALSO include within an Apache product a documented,
non-default, build option to allow users to explicitly choose to
validate, retrieve, or configure any system requirement for an Apache
product, provided that such option is not likely to be confused with
the standard product build and that any resulting retrieval of a
prohibited work is accompanied by a clear identification of its
associated license.

I certainly don't want to do anything that could get us in legal
trouble, but if we're allowed to download this to make everyone's life
a bit easier, let's do it.

Not to re-beat a dead horse, but I'm looking over things and I'm
wondering if in the rush to get 4.8.0 ready to go if it's possible
that we may have misinterpreted what Bertrand said?

Here's a link to the original JIRA issue:
Here's a link to the e-mail mentioning the clarifications in that
issue which was FLEX-53 but is now FLEX-33089 making it allowed to be
a build step:

I hope that's the case as it would probably mean that at the least we
can automatically download playerglobal and airglobal as part of the
build process and make it that much easier for someone to build their
own SDK and contribute their changes back.


> So, there is no way to auto-download that within Apache rules AFAICT.  We
> could go through the process of becoming making Apache an Adobe
> re-distributor, but I'm not sure that's worth the effort.  It also possible
> that Spoon or some other entity could become and Adobe redistributor and
> distribute its own packages that look much more like what Adobe SDKs do
> today.
>> Also, was the BlazeDS support defaulted to 'no' because it's optional
>> and is currently a huge download or was the reasoning based on the
>> license?
>> Jeff
> BlazeDS is optional.  You can write apps without it.  We had to make it
> optional because it is under MPL at this time.
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.

View raw message