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.
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".
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. 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.
