Justin, Just changing the build scripts alone are not sufficient. We need to verify and regress TLF 3.0 with the current Flex SDK code before we can include it in our scripts. As Alex mentioned in the "TLF and Flex" thread, TLF sometimes changes in a way that needs code changes in the Flex SDK.
Conversely, if TLF is donated to Apache, we may get to make changes to TLF directly to keep things smooth. Thanks, Om On Tue, Feb 28, 2012 at 4:53 PM, Justin Mclean <jus...@classsoftware.com>wrote: > Hi, > > > I don't believe projects that fall under the ASF banner can make > > improvements or updates or references to non-ASF projects. > I'm suggesting improving our build scripts not the TLF library. > > > I believe TLF is still an Adobe product, even the older version, and I > > think, by "Building" TLF's source into a binary, it might become an > issue. > We are currently doing that with version 1.0 so linking to another version > of the same product is the same I think. > > The code is here: > http://sourceforge.net/projects/tlf.adobe/ > > And it's currently under a Mozilla Public Licence 1.1. > > This comes under Category B 3rd party licence.[1] My reading (which may > be wrong) is that there is no issue in using the binary and as we are not > modifying the source code we are not creating a derivate work. > > Thanks, > Justin > > [1] http://www.apache.org/legal/3party.html
