> >> On Wed, Jun 13, 2012 at 1:26 PM, Frank Zhang <frank.zh...@citrix.com> > >> wrote: > >> > I still have some concerns about using ant. > >> > As we are removing those apache incompatible jars from source code, > >> there build process would break as those jars are compilation > dependencies. > >> > Speaking for Ant(not maven), how other projects handle this? Do we > >> > need > >> to put those jar to somewhere and pull it before compiling? Then we > >> are doing what maven did. > > > > Jnetcap is one of them. BuildRequires is not enough, it won't work for > > developers who only uses ant > > > > It's a bigger problem in that even if we were using something like Maven > which automagically downloads dependencies, we couldn't do so as part of > the default build based on my reading of > http://www.apache.org/legal/3party.html > > Which says: > YOU MUST NOT distribute build scripts or documentation within an Apache > product with the purpose of causing the default/standard build of an Apache > product to include any part of a prohibited work.
This gives me a shock! I can't believe ASF project never uses any LGPL library. > > So either it's a system requirement - OR...we get rid of it and remove > anything that depends on it. (is the dhcp listener the only part that > does?) The problem is we can't predict we may need LGPL library in future, though we can get rid of what we already have. > > --David
