On 4/26/12 12:22 AM, "Bertrand Delacretaz" <bdelacre...@apache.org> wrote:
>
> What's that Adobe license exactly? URL?
http://www.adobe.com/products/eulas/pdfs/adobe_flex_software_development_kit
-combined-20110916_0930.pdf
>
>
>> 3. Since these are required files, we cannot download them as part of the
>> build script.
>
> Not automatically, but if the user needs to take active action to
> confirm that they accept using those files, and us encouraging them to
> do so is not illegal, the build could download them.
>
> However, if Flex cannot work without them we have a problem - required
> dependencies of an Apache product must have compatible licenses.
>
> If you can document (in JIRA I'd say) what makes you consider those
> files as build tools, that relaxes some of the licensing requirements
> as described at http://apache.org/legal/resolved.html#build-tools
>
In JIRA under the Flex project?
Is there yet another distinction between "prerequisites" and "build tools"?
I see other projects say that you have to download a JDK as a prerequisite.
That's basically what I'm proposing here, although Adobe is the only
supplier of a usable SDK. Before getting the Apache Flex distribution, you
would download and install Ant, a JDK (to build the compiler), and the Adobe
FlashPlayer and/or Adobe AIR SDKs. I don't think we need to actually
include these files in a distribution other than as a convenience and then
only if we can get redistribution rights.
There is no code in these files that go into the output executable. They
represent the classes in the VM/runtime. Roughly the equivalent of
java.lang and java.awt. Some of the other files are utility applications
used to package the executable for installation on a mobile platform, or for
launching the runtime in debug mode.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
