On Fri, Nov 4, 2016 at 4:27 PM, Bertrand Delacretaz wrote:
> IMO the "can Apache projects rely on components under prohibited > licenses?" section of http://apache.org/legal/resolved.html applies, > and the key question is then whether the external component's license > terms affect the NetBeans product's licensing. In the above reference, I see this: "For example, using a GPL'ed tool during the build is OK." That's the case of nb-javac in the context of the optional module provided by the "java" cluster. The core cluster, i.e., "platform" does not need the "java" cluster to build. The nb-javac libraries can be installed separately from NetBeans itself, via the installer or a related update mechanism. Gj On Fri, Nov 4, 2016 at 4:27 PM, Bertrand Delacretaz <bdelacre...@apache.org> wrote: > Hi, > > Creating a new thread as this now off-topic w.r.t to including things > in the donation or not. > > On Fri, Nov 4, 2016 at 4:06 PM, Ate Douma <a...@douma.nu> wrote: > > ...The question, as I see it, being: > > > > Will the Apache NetBeans project be allowed to develop and release > > a (or more) optional module, the Java Editor module in casu, under the > > ASL 2.0 license at the ASF, which depends on external 3rd party module > > nb-javac which is available under the GPL v2 w/ CPE (Category X). > > End users willing to use the optional module will be required to > provide > > the nb-javac module themselves during installation. > > > > I think this is a great way to formulate the issue. > > IMO the "can Apache projects rely on components under prohibited > licenses?" section of http://apache.org/legal/resolved.html applies, > and the key question is then whether the external component's license > terms affect the NetBeans product's licensing. > > If for example NetBeans depends on GPL licensed APIs that would be an > obstacle IMO. > > OTOH if the affected modules can be released under our license with no > impact from those GPL modules everything's fine, IMO. > > -Bertrand >
