On Sun, Nov 06, 2005 at 11:23:49AM -0500, Henri Yandell wrote: > So at least 5 LGPL jars and 4 BCL jars. As far as I know, we're not meant > to have these in SVN, and that the imports on the LGPL jars are not meant > to be in SVN either.
Correct. The official ASF policy today is "No LGPL dependencies in Java projects." As you mention, the board has discussed allowing LGPL for Java projects but any resolution stating that has been tabled indefinitely. A small part of the reason for the delay is that we've been told Eben Moglen from the FSF will be issuing an opinion clarifying the relationship between LGPL and Java. However, none of the board's discussions around LGPL have discussed allowing any LGPL code to be checked into the ASF Subversion repository. What has been discussed is allowing an ASF project, under the ALv2 license, to optionally *use* but not *distribute* LGPL code. If a project requires LGPL code to operate, the board has discussed a one-year exception to remove that hard dependency. Plus, if an ASF project wants to use an LGPL library, end users will have to fetch the LGPL dependencies themselves. However, none of this has been approved by the Board. There might be some eventual wiggle room in allowing re-distribution in end-user releases, but that would have to be hammered out. -- justin
