Just a clarification here. It is fine to use, or depend on proprietary software that exists on the system. During the build, or after install. "For example, using a GPL'ed tool during the build is OK." [1] The stipulation is that we cannot ship anything WITH the build that is incompatible with our license.
[1] http://www.apache.org/legal/resolved.html On Thu, Sep 13, 2012 at 8:13 PM, David Nalley <da...@gnsa.us> wrote: > On Thu, Sep 13, 2012 at 3:03 PM, Rohit Yadav <rohit.ya...@citrix.com> > wrote: > > > >>But how do you build them without those libraries - for instance the > >>VMware plugin doesn't build without the vmware libraries being > >>present. > > > > No, not vmware plugin or any nonoss plugin. > > By default mvn builds only oss ones. > > > > So if you've the non-oss jars, you copy them to deps/ and run the > install-non-oss.sh script. > > This will copy the nonoss deps to ~/.m2 and you build with the nonoss > profile: > > mvn package -Pnonoss, this creates packages with these nonoss plugins. > > (check plugin/pom.xml, that will clear the confusion). > > > > Lastly, why is kvm under nonoss in plugin/pom.xml? Thanks. > > > Because until today the libvirt-java library that it needed was LGPL > which is not compliant with the ASF guidelines for permissible > licenses to be included/depended on by the default build. > > --David > -- NS
