I will attempt to provide an answer, but if it becomes a debate we will move it to legal-discuss.
On 7/16/14 12:11 AM, "Justin Mclean" <jus...@classsoftware.com> wrote: >Hi, > >> I see, you are claiming the compiled results should copy an >> incompatibly-licensed file into the resulting folders. > >How is that different to what we do for player global swc? It isn't. We don't copy that file either as part of the default build scripts. > >> AIUI, even compiled results cannot do that for required features. > >Please tell me where this rule is specified as I've not run into it >before, and it's probably a concern given the location of player gloabal >swfs + other files we copy into the SDK. Does the installer also need to >change where it copies files if this is the case? You may have misunderstood me. It is my understanding that the build scripts in the source package cannot copy category X files for required features. That is my takeaway from the guidance of our mentors during incubation. That's why the default build.xml requires PLAYERGLOBAL_HOME and AIR_HOME. These are build prerequisites and not dependencies per-se, and are pre-installed by the source package consumer before running the build, and you have to be able to compile and run without copying that stuff into the Apache Flex distribution (which I verified last night). Only optional features can require category X files and that's why our default build has always asked about embedded fonts and BlazeDS but not about AIR. I suppose we could argue that AIR is an optional feature, though... The mentors agreed that the Installer and scripts in the IDE can copy stuff around (with appropriate warnings and acceptance of licenses.d Pretty sure that's why we are setup the way we are, with scripts in a separate folder, otherwise I think the default build script would have asked about copying more things into the result folders. -Alex
