[opencms-dev] LGPL

[Alexander Kandzior]

Robert,

all of the files listed below are considered to be part of the library,
and the LGPL applies to all modifications here. If you add your own
module to OpenCms with the integrated module mechanism, then this is not
a part of the library but a work using the library, so the LGPL does not
apply. 

Best Regards,
Alex.

Alexander Kandzior
Alkacon Software - The OpenCms Experts
http://www.alkacon.com

> -----Original Message-----
> From: owner-opencms-dev at www.opencms.org 
> [mailto:owner-opencms-dev at www.opencms.org] On Behalf Of Robert Jean
> Sent: Monday, March 24, 2003 5:25 AM
> To: opencms-dev at opencms.org
> Subject: [opencms-dev] LGPL
> 
> 
> Hello,
> 
> OpemCms is distributed under the LGPL license. I would
> be grateful to anyone who could explain me which part
> is considered as being part of the library, and which
> parts is not. In particular, I would like to know if
> these files are part of the library:
> 
> *.java files
> *.jsp files
> *.html files
> *.xml files
> *.gif files
> 
> The situation might be more complex than what I have
> depicted here. Please detail.
> 
> This question is triggered by a down-to-earth
> consideration. In case I want for instance to modify
> the look and feel of OpenCms, or add/remove/modify
> some of its features, what can I protect with my own
> license and what do I have to release with the source
> code? In most cases, I would be happy to release the
> source code, knowing that it could help people who
> made this great source code base available in the
> first place. In a few instances, it would be
> problematic, intellectual property linked to sensitive
> issues being a concern to my organization.
> 
> Thank you,
> Robert
> 
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your 
> desktop! http://platinum.yahoo.com
>