I'm working on a project that will be using an unmodified version of BlazeDS, and have been trying to understand what the making available requirements are for the source code.聽 It doesn't look like it is possible to ship the blazeds source zip download itself - specifically:
1) the ''opt'' source module contains 3rd party jars under modules/opt/lib, like weblogic.jar, jrun.jar, etc. that don't seem to be licensed themselves.聽 At least there is no mention of them in the top level blazesds-src-readme.htm file.聽 But these are required for building files in the opt module.
2) the jrun.jar includes cryptography related software, JSafe, that might not be legal to export from the US without going through an export approval process.
The BlazeDS source download is pretty big - and includes a lot of other pieces, like qa, frameworks ( with datavisualization.swc), etc. that aren't directly related to building the Java source.
From Adobe's/the BlazeDS groups viewpoint - for the purposes of the LGPL v3 license that BlazeDS is under, which part of the source download needs to be made available to a customer?聽 Do you consider this to be the whole src download, or just a portion of the modules directory?
If it is the whole source download, then how are the non-Open Source jars not mentioned in the blazeds-src-readme.htm file licensed, and how do they relate to the LGPL v3?
I couldn't find many license related questions in the forum - I'm not sure if I'm understanding the LGPL v3 source distribution requirements, or if groups have tackled the making available requirements some other way.聽 But it seems like any product shipped using the BlazeDS jars is going to have the same questions.
Thanks,
聽 Carlos
聽 carlos.bonilla@hp.com
Requirements for BlazeDS lgpl v3 source...Hi Carlos. Here is a blog posting from the BlazeDS product manager that talks about the licensing. I've also asked him to respond to this thread directly.
http://anilchannappa.org/2009/04/15/blazedslgpl/
Hope that helps.
-Alex
No comments:
Post a Comment