On 11/7/05, Anil Gangolli <[EMAIL PROTECTED]> wrote: > Inline comments below... > Henri Yandell wrote: > > > > >For 2.0 I think we should be trying to get a clear LGPL message, or > >proto-message; and get things dealt with prior to the release. > > > >Effectively this means: > > > >1) Removing 'bad' jars from SVN. > >2) Modifying install process/build instructions to instruct user to > >download the relevant jars themselves. > > > > > For item (2), I'd like to understand the boundary of what we can do. > For example, can we provide ant scripts / other build infrastructure > that is generic, and configured specifically to download these jars? If > so, we should start building a network-based pre-build target and an > installer in the Roller 2.x line.
Usually the legality is that the user has to initiate the download. It's an issue lots of things have (Netbeans has it I think), often with the BCL licensed things. JAMES probably have a good strategy which we can use. > >3) Ensuring nobody is concerned with the various usages of LGPL'd code. > > > >Hen > > > > > For Hibernate, we do import org.hibernate.* classes and use Hibernate > APIs directly currently. So we are currently in the "worst" category of > "offenders". Not so bad; the worst part is having the jars in SVN. The legality of being allowed to import org.hibernate.* is pretty much all cleared up, the question is over the policy. Should ASF projects depend on LGPL or should it not. Historically the answer was that yes they can, but only for optional features. Currently it's suggested that they can for required features too, but with a time limit (1 year currently the floated time). > A JSR-220-based rewrite would entail quite a bit of effort for 2.0, and > I think will force us to require Java 5 / JDK 1.5.x. Yep, looks like Java 5. :( > The main thing > that bugs me about this direction is the cramped timing with respect to > the maturity levels of JSR 220 and the Hibernate support for it, > although alternate supporting implementations might be considered along > this line as well. Yep, though we would have a time period in which to get it done (and for Hibernate to mature its JSR 220 support). Hen
