Ok ... found a much cooler way to avoid this completely ... so no worries ... no new Jars with bad licenses :-)
Chris ________________________________________ Von: Justin Mclean <jus...@classsoftware.com> Gesendet: Mittwoch, 12. November 2014 01:04 An: dev@flex.apache.org Betreff: Re: [FLEX-JS] Streamlining the packaging Hi, > I would prefer to not have Apache Flex releases use code with licenses > that have “bad” words in it, which appears to be the case for the > https://code.google.com/p/reflections/ library. I would not like the > Installer to have to offer up those bad words for approval by the > customer. And, if we decide to bundle that jar some day, our LICENSE file > will have to have those same bad words in it. BTW don't believe it actually required to show the user, let alone accept, the license for compatible licenses. Still may be useful for the user to know of course, but the whole point of being compatible is that it gives you the same rights as an Apache license. There's is no EULA for MPL [1], this was made explicit as FireFox putting in a EULA, it was quickly removed. [2][3] Justin 1. https://www.mozilla.org/en-US/about/legal/eula/ 2. http://blog.lizardwrangler.com/?p=379 3. http://blog.lizardwrangler.com/?p=371
