We don't need to replace the Java code that depends on LGPL deps, as long as we:
1. Don't download the LGPL dep jars in the normal build
2. Don't ship the LGPL jars in our release
Therefore, I've split the build so that the classes that depend on LGPL jars won't be compiled in the standard build.
You have to execute 'compile-optional' to pull down those LGPL jars and compile the related code.
The question is how this applies to unit tests. If you interpret "default build" to be the one that runs when you just
type "ant", then typing 'ant test' could pull down LGPL jars, compile the code and its unit tests without problems. I'm
pulling for this interpretation :)
Don
Rainer Hermanns wrote:
Ted,
thanks for clearifying this...
Just removed the hibernate dep from ivy/pom. Hibernate was not used
within the codebase, only in the docs.
Do the docs need to be cleared as well from those deps (just the written
docs, not code samples)?
Has anyone yet talked to the JasperReports guy?
This would be a dependency really hard to replace...
cheers,
Rainer
On 3/25/06, Rainer Hermanns <[EMAIL PROTECTED]> wrote:
How should those be "refactored"? Is there a guideline available for
removing the "bad" deps?
First, we should contact the authors and make sure they do want to put
the code under the LGPL. Sometimes people use that as a default and
don't actually care.
If the author does care, then we have to find or create comparable
technology under a license that we can bundle with the Apache License,
without trespassing on anyone's IP.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
