======================================== http://www.apache.org/legal/resolved.html#prohibited
Can Apache projects rely on components under prohibited licenses? Apache projects cannot distribute any such components. As with the previous question on platforms, the component can be relied on if the component's licence terms do not affect the Apache product's licensing. For example, using a GPL'ed tool during the build is OK. Can Apache projects rely on components whose licensing affects the Apache product? Apache projects cannot distribute any such components. However, if the component is only needed for optional features, a project can provide the user with instructions on how to obtain and install the non-included work. Optional means that the component is not required for standard use of the product or for the product to achieve a desirable level of quality. The question to ask yourself in this situation is: "Will the majority of users want to use my product without adding the optional components?" ======================================== It's hard to tell without seeing the committed files, but is this dependency referenced by anything outside of the build scripts/config files? If it is only used indirectly by our build process, then we probably can have it as a dependency. If it is directly referenced by our tests, then I would say we should not have this as a dependency, since any code that references it is now polluted by the viral nature of LGPL. On Sat, Aug 30, 2014 at 7:21 AM, Andrus Adamchik <and...@objectstyle.org> wrote: > Another one of Alex's patches adds a <scope>test</scope> dependency on > org.fluttercode.datafactory:datafactory, which helps assembling complex test > object trees. One caveat is that Datafactory is under LGPL: > > https://github.com/andygibson/datafactory/blob/master/license.txt > > I am about 80% certain that this is ok for a unit test dependency, but maybe > someone knows of precedents on other apache projects and can confirm this? > > Andrus
