www-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

www/licenses lgpl-java.html


From: Ineiev
Subject: www/licenses lgpl-java.html
Date: Sat, 20 Nov 2021 05:21:21 -0500 (EST)

CVSROOT:        /web/www
Module name:    www
Changes by:     Ineiev <ineiev> 21/11/20 05:21:21

Modified files:
        licenses       : lgpl-java.html 

Log message:
        Finalize updating to 1.96, remove odd spaces, unreduce line width.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/lgpl-java.html?cvsroot=www&r1=1.29&r2=1.30

Patches:
Index: lgpl-java.html
===================================================================
RCS file: /web/www/www/licenses/lgpl-java.html,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -b -r1.29 -r1.30
--- lgpl-java.html      7 Apr 2021 17:55:37 -0000       1.29
+++ lgpl-java.html      20 Nov 2021 10:21:20 -0000      1.30
@@ -1,15 +1,14 @@
-<!--#include virtual="/server/html5-header.html" -->
+<!--#include virtual="/server/header.html" -->
 <!-- Parent-Version: 1.96 -->
 <title>The LGPL and Java
 - GNU Project - Free Software Foundation</title>
 <!--#include virtual="/licenses/po/lgpl-java.translist" -->
 <!--#include virtual="/server/banner.html" -->
-<h2 class="c">The LGPL and Java</h2>
+<h2>The LGPL and Java</h2>
 
-<address class="byline c">by <a
+<address class="byline">by <a
 href="mailto:licensing@fsf.org";>David Turner</a></address>
 
-<div class="reduced-width">
 <hr class="no-display" />
 <div class="announcement">
 <p>This article was written in November 2004, when <a
@@ -21,9 +20,7 @@
 </div>
 <hr class="thin" />
 
-<div class="article">
-<p>
-It has always been the FSF's position that dynamically linking
+<p>It has always been the FSF's position that dynamically linking
 applications to libraries creates a single work derived from both the
 library code and the application code.  The GPL requires that all
 derivative works be licensed as a whole under the terms of the GPL, an
@@ -31,33 +28,32 @@
 application links to a library licensed under the GPL, the application
 too must be licensed under the GPL.  By contrast, libraries licensed
 under the GNU Lesser General Public License (LGPL) may be linked to
-proprietary applications. </p>
-<p>
+proprietary applications.</p>
 
-In July of 2003, Slashdot published a story claiming that I had claimed
+<p>In July of 2003, Slashdot published a story claiming that I had claimed
 that the LGPL did not function as intended in the case of Java.  This
 story was based on a misunderstanding of a response to a question sent
 to licensing@gnu.org, and many attempts to clarify the issue in the
 Slashdot story did not get across.  I have received numerous questions
-about the story since, via both licensing@gnu.org and personal email. </p> 
-<p>
-FSF's position has remained constant throughout: the LGPL works as
+about the story since, via both licensing@gnu.org and personal email.</p>
+
+<p>FSF's position has remained constant throughout: the LGPL works as
 intended with all known programming languages, including Java.
 Applications which link to LGPL libraries need not be released under
 the LGPL.  Applications need only follow the requirements in section 6
 of the LGPL: allow new versions of the library to be linked with the
-application; and allow reverse engineering to debug this. </p> 
-<p>
-The typical arrangement for Java is that each library an application
+application; and allow reverse engineering to debug this.</p>
+
+<p>The typical arrangement for Java is that each library an application
 uses is distributed as a separate JAR (Java Archive) file.
 Applications use Java's &ldquo;import&rdquo; functionality to access classes 
from
 these libraries.  When the application is compiled, function
 signatures are checked against the library, creating a link.  The
 application is then generally a derivative work of the library.  So,
 the copyright holder for the library must authorize distribution
-of the work.  The LGPL permits this distribution. </p> 
-<p>
-If you distribute a Java application that imports LGPL libraries, it's
+of the work.  The LGPL permits this distribution.</p>
+
+<p>If you distribute a Java application that imports LGPL libraries, it's
 easy to comply with the LGPL.  Your application's license needs to
 allow users to modify the library, and reverse engineer your code to
 debug these modifications.  This doesn't mean you need to provide
@@ -65,21 +61,19 @@
 course, some changes the users may make to the library may break the
 interface, rendering the library unable to work with your application.
 You don't need to worry about that&mdash;people who modify the library
-are responsible for making it work. </p> 
-<p>
-When you distribute the library with your application (or on its own),
+are responsible for making it work.</p>
+
+<p>When you distribute the library with your application (or on its own),
 you need to include source code for the library.  But if your
 application instead requires users to obtain the library on their own,
-you don't need to provide source code for the library. </p> 
-<p>
-The only difference between Java and C from the LGPL's perspective is
+you don't need to provide source code for the library.</p>
+
+<p>The only difference between Java and C from the LGPL's perspective is
 that Java is an object-oriented language, supporting inheritance.  The
 LGPL contains no special provisions for inheritance, because none are
 needed.  Inheritance creates derivative works in the same way as
 traditional linking, and the LGPL permits this type of derivative work
-in the same way as it permits ordinary function calls. </p> 
-</div>
-</div>
+in the same way as it permits ordinary function calls.</p>
 
 </div><!-- for id="content", starts in the include above -->
 <!--#include virtual="/server/footer.html" -->
@@ -138,7 +132,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2021/04/07 17:55:37 $
+$Date: 2021/11/20 10:21:20 $
 <!-- timestamp end -->
 </p>
 </div>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]