You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-commits@db.apache.org by rh...@apache.org on 2020/01/12 20:49:39 UTC

svn commit: r1872688 - in /db/derby/code/branches/10.15: RELEASE-NOTES.html releaseSummary.xml

Author: rhillegas
Date: Sun Jan 12 20:49:39 2020
New Revision: 1872688

URL: http://svn.apache.org/viewvc?rev=1872688&view=rev
Log:
DERBY-6066: First rev of release notes for 10.15.2.0; commit derby-7066-01-aa-releaseNotes-firstRev.diff.

Modified:
    db/derby/code/branches/10.15/RELEASE-NOTES.html
    db/derby/code/branches/10.15/releaseSummary.xml

Modified: db/derby/code/branches/10.15/RELEASE-NOTES.html
URL: http://svn.apache.org/viewvc/db/derby/code/branches/10.15/RELEASE-NOTES.html?rev=1872688&r1=1872687&r2=1872688&view=diff
==============================================================================
--- db/derby/code/branches/10.15/RELEASE-NOTES.html (original)
+++ db/derby/code/branches/10.15/RELEASE-NOTES.html Sun Jan 12 20:49:39 2020
@@ -1,10 +1,10 @@
 <html lang="en">
-<title>Release Notes for Apache Derby 10.15.1.3</title>
+<title>Release Notes for Apache Derby 10.15.2.0</title>
 <body>
 <h1>
-<a name="Release Notes for Apache Derby 10.15.1.3"></a>Release Notes for Apache Derby 10.15.1.3</h1>
+<a name="Release Notes for Apache Derby 10.15.2.0"></a>Release Notes for Apache Derby 10.15.2.0</h1>
 <div>
-<p>These notes describe the difference between Apache Derby release 10.15.1.3 and the preceding release 10.14.2.0.</p>
+<p>These notes describe the difference between Apache Derby release 10.15.2.0 and the preceding release 10.15.1.3.</p>
 </div>
 <ul>
 <li>
@@ -75,23 +75,10 @@ The 10.15 release family supports the fo
 
 
 <p>
-This is a feature release. The following new feature was added:
+This is a maintenance (bugfix) release. No new features were added.
 </p>
 
 
-<ul>
-
-
-<li>
-<b>JPMS modularization</b> - Derby has been re-packaged as a set of JPMS modules. This introduced a new jar file, <i>derbyshared.jar</i>, required by all configurations. Module diagrams for Derby configurations can be found in the
-<a href="https://db.apache.org/derby/docs/10.15/publishedapi/index.html">javadoc</a>
-for the 10.15 public API.
-</li>
-
-
-</ul>
-
-
 <p>
 New users should consult the
 <a href="https://db.apache.org/derby/manuals/index.html#docs_10.15">10.15 documentation</a>,
@@ -100,27 +87,11 @@ especially the
 </p>
 
 
-<p>
-Existing users who want to continue running Derby with a classpath should read the extended release note for issue DERBY-6945 (see below).
-</p>
-
-
-<p>
-Existing users who want to run Derby with a module path should consult the module diagrams in the
-<a href="https://db.apache.org/derby/docs/10.15/publishedapi/index.html">javadoc</a>
-for the 10.15 public API. Templates for wiring together a module path can be found in the
-<i>setEmbeddedCP</i>, <i>setNetworkServerCP</i>, and <i>setNetworkClientCP</i> scripts located
-in the bin directory of the release distributions, as described by the
-"Manually setting the CLASSPATH/MODULEPATH environment variables" topic in the
-<a href="https://db.apache.org/derby/docs/10.15/getstart/index.html">Getting Started With Derby</a> guide.
-</p>
-
-
 </div>
 <h2>
 <a name="Bug Fixes"></a>Bug Fixes</h2>
 <div>
-<p>The following issues are addressed by Derby release 10.15.1.3. These issues are not addressed in the preceding 10.14.2.0 release.</p>
+<p>The following issues are addressed by Derby release 10.15.2.0. These issues are not addressed in the preceding 10.15.1.3 release.</p>
 <table border="2">
 <tr>
 <th>
@@ -128,251 +99,38 @@ in the bin directory of the release dist
 </th><th>Description</th>
 </tr>
 <tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-7020">DERBY-7020</a></td><td>Fix release targets to account for modularization changes</td>
-</tr>
-<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-7018">DERBY-7018</a></td><td>Test the demo programs after the changes made by DERBY-6945</td>
-</tr>
-<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-7016">DERBY-7016</a></td><td>Adjust the set*CP scripts to include derbyshared.jar and to set a MODULEPATH variable as well</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-7038">DERBY-7038</a></td><td>Upgrade ant version and re-write javadoc build targets to use improved &lt;javadoc&gt;task</td>
 </tr>
 <tr>
-<td><a
-  href="https://issues.apache.org/jira/browse/DERBY-6981">DERBY-6981</a></td><td>"SQLSTATE: XJ001, SQLERRMC: java.lang.NullPointerException  XJ001.U"</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-7040">DERBY-7040</a></td><td>Add dependency stanzas to maven poms</td>
 </tr>
 <tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6980">DERBY-6980</a></td><td>Documentation changes to accompany jigsaw-modularization of derby</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-7041">DERBY-7041</a></td><td>null pointer exception when creating view based on other views</td>
 </tr>
 <tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6973">DERBY-6973</a></td><td>Provide SHA-512 checksums on future releases</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-7046">DERBY-7046</a></td><td>NoClassDefFoundError on java -jar derbynet.jar</td>
 </tr>
 <tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6945">DERBY-6945</a></td><td>Re-package Derby as a collection of jigsaw modules</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-7052">DERBY-7052</a></td><td>Reordering and (mildly) reorganizing build.xml Ant targets around buildsource</td>
 </tr>
 <tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6856">DERBY-6856</a></td><td>Make it possible to build Derby using JDK 9</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-7053">DERBY-7053</a></td><td>Further top build.xml streamlining</td>
 </tr>
 <tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-5543">DERBY-5543</a></td><td>include debug info in derby builds uploaded to maven</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-7057">DERBY-7057</a></td><td>Unreferenced failing target in main build</td>
 </tr>
 </table>
 </div>
 <h2>
 <a name="Issues"></a>Issues</h2>
 <div>
-<ul>
-<li>
-<a href="#Note for DERBY-6945"><span>Note for DERBY-6945: 
-Modularize Derby, cleanly partitioning its packages across a small set of
-JPMS components.
-</span></a>
-</li>
-</ul>
-<p>Compared with the previous release (10.14.2.0), Derby release 10.15.1.3 introduces the following new features and incompatibilities. These merit your special attention.</p>
-<hr>
-<h3>
-<a name="Note for DERBY-6945"></a>Note for DERBY-6945</h3>
-<div>
-
-<!-- 
-  SUMMARIZE THE ISSUE. This is a one line, one sentence summary of the
-  issue. It serves as the title for the issue in the Issues section of
-  the full Release Notes.
-
-  For instance:
-
-  Applications may no longer open two InputStreams on the same ResultSet column.
--->
-
-
-<h4>Summary of Change</h4>
-
-<p>
-Modularize Derby, cleanly partitioning its packages across a small set of
-JPMS components.
-</p>
-
-
-<!-- 
-  DESCRIBE WHAT IT IS THAT THE USER ACTUALLY SEES WHEN THE PROBLEM OCCURS.
-
-  For instance:
-
-  In the previous release, applications were able to open two
-  InputStreams on the same column. Depending on how these streams
-  interacted, the value siphoned out of the column was erratic. Now
-  Derby raises a SQLException when the application attempts to create
-  the second InputStream.
--->
-
-
-<h4>Symptoms Seen by Applications Affected by Change</h4>
-
-<p>
-A new jar file (<i>derbyshared.jar</i>) has been added. All Derby
-configurations require it. In addition, the <i>derbytools.jar</i> library is
-now required when running the network server and/or when using Derby
-DataSources.
-</p>
-
-
-<p>
-Slightly different privileges must be granted to the Derby jar files when running
-under a Security Manager.
-</p>
-
-
-<p>
-Derby jar files can now be wired into a module path
-for use by module-aware applications.
-</p>
-
-
-<!-- 
-  OPTIONAL: DESCRIBE INCOMPATIBILITIES WITH PREVIOUS RELEASE, IF ANY.
-
-  For instance:
-
-  Applications which open two InputStreams on the ResultSet column now
-  fail.
--->
-
-
-<h4>Incompatibilities with Previous Release</h4>
-
-<p>
-Legacy applications may fail if their classpaths don't contain the
-required jar files. Code common to all Derby configurations has been
-isolated in the new <i>derbyshared.jar</i> file. DataSources have
-moved from <i>derbyclient.jar</i> and <i>derby.jar</i> into <i>derbytools.jar</i>
-
-</p>
-
-
-<p>
-Legacy applications which run under a Java SecurityManager may fail
-due to insufficient privilege grants.
-</p>
-
-<!-- 
-  DESCRIBE WHY THE CHANGE WAS MADE.
-
-  For instance:
-
-  The previous behavior violated the JDBC standard. The new behavior
-  is correct.
--->
-
-
-<h4>Rationale for Change</h4>
-
-<p>
-Derby was divided into JPMS components for the following reasons:
-</p>
-
-
-<ul>
- 
-<li>
-<b>Footprint</b> - Modularization reduces Derby's footprint
- when running embedded on resource-constrained devices.</li>
- 
-<li>
-<b>Security</b> - Modularization lets Derby protect its code
- via package-level encapsulation.</li>
-
-</ul>
-
-
-<!-- 
-  OPTIONAL: DESCRIBE HOW TO REVERT TO THE PREVIOUS BEHAVIOR OR
-  OTHERWISE AVOID THE INCOMPATIBILITIES INTRODUCED BY THIS CHANGE.
-
-  For instance:
-
-  Users must recode applications which open multiple streams on the same column.
--->
-
-
-<h4>Application Changes Required</h4>
-
-<p>
-Consult the module diagrams for configurations described on the
-landing page of the
-<a href="https://db.apache.org/derby/docs/10.15/publishedapi/index.html">10.15 public API</a>.
-Then adjust your application's classpath as follows:
-</p>
-
-
-<ul>
- 
-<li>
-<b>Remote client</b> - When running remote client applications, make
- sure that the classpath includes <i>derbyshared.jar</i>. Remote applications which
- use Derby DataSources should also include <i>derbytools.jar</i>.</li>
- 
-<li>
-<b>Embedded engine</b> - When running the embedded engine, make
- sure that the classpath includes <i>derbyshared.jar</i>. Embedded applications which
- use Derby DataSources should also include <i>derbytools.jar</i>.</li>
- 
-<li>
-<b>Network server</b> - When running the network server, make
- sure that the classpath includes <i>derbyshared.jar</i> and
- <i>derbytools.jar</i>. This is not necessary if you boot the server
- via the <i>java -jar derbyrun.jar</i> pattern. <i>derbyrun.jar</i>
- sets up its own classpath correctly.</li>
- 
-<li>
-<b>Tools</b> - When running Derby tools like <i>ij</i>,
- <i>dblook</i>, and <i>sysinfo</i>, make
- sure that the classpath includes <i>derbyshared.jar</i>. Again, no
- change should be necessary if you boot the tools via the <i>java -jar
- derbyrun.jar</i> pattern.</li>
-
-</ul>
-
-
-<p>
-Java security policy files must grant slightly different privileges to
-Derby jar files. This is because packages have moved to different
-ProtectionDomains (chiefly into <i>derbyshared.jar</i>) and because an
-additional
-privilege is needed in order to read the module path. For more information, see the
-<a href="https://db.apache.org/derby/docs/10.15/security/csecjavasecurity.html"><i>Configuring Java Security</i></a>
-topic in the <b>Derby Security Guide</b> and consult
-the following template policy files
-in the <i>demo/templates</i> directory of the bin distribution:
-</p>
-
-
-<ul>
- 
-<li>
-<b>clientTemplate.policy</b> - Privileges needed by remote
- client applications.</li>
- 
-<li>
-<b>engineTemplate.policy</b> - Privileges needed by applications
- which embed the Derby engine.</li>
- 
-<li>
-<b>serverTemplate.policy</b> - Privileges needed when running the
- network server.</li>
- 
-<li>
-<b>toolsTemplate.policy</b> - Privileges needed when running
- Derby tools.</li>
-
-</ul>
-
-
-</div>
+<ul></ul>
+<p>No issues required detailed release notes.</p>
 </div>
 <h2>
 <a name="Build Environment"></a>Build Environment</h2>
 <div>
-<p>Derby release 10.15.1.3 was built using the following environment:</p>
+<p>Derby release 10.15.2.0 was built using the following environment:</p>
 <ul>
 <li>
 <b>Branch</b> - Source code came from the 10.15 branch.</li>
@@ -399,7 +157,7 @@ ensures that the file came from a certai
 <a href="https://www.pgpi.org/">PGP</a> or
 <a href="https://www.gnupg.org/">GPG</a>.
 First download the Apache Derby
-<a href="https://dist.apache.org/repos/dist/release/db/derby/KEYS">KEYS</a>
+<a href="https://www.apache.org/dist/db/derby/KEYS">KEYS</a>
 as well as the <code>asc</code> signature file for the particular
 distribution. It is important that you get these files from the ultimate
 trusted source - the main ASF distribution site, rather than from a mirror.

Modified: db/derby/code/branches/10.15/releaseSummary.xml
URL: http://svn.apache.org/viewvc/db/derby/code/branches/10.15/releaseSummary.xml?rev=1872688&r1=1872687&r2=1872688&view=diff
==============================================================================
--- db/derby/code/branches/10.15/releaseSummary.xml (original)
+++ db/derby/code/branches/10.15/releaseSummary.xml Sun Jan 12 20:49:39 2020
@@ -33,7 +33,7 @@ with real information.
     E.g.: 10.2.1.7
 
 -->
-<previousReleaseID>10.14.2.0</previousReleaseID>
+<previousReleaseID>10.15.1.3</previousReleaseID>
 
 <!--
     Identifier(s) of previously released versions. Any issue that was fixed in
@@ -95,18 +95,9 @@ The 10.15 release family supports the fo
 <newFeatures>
 
 <p>
-This is a feature release. The following new feature was added:
+This is a maintenance (bugfix) release. No new features were added.
 </p>
 
-<ul>
-
-<li><b>JPMS modularization</b> - Derby has been re-packaged as a set of JPMS modules. This introduced a new jar file, <i>derbyshared.jar</i>, required by all configurations. Module diagrams for Derby configurations can be found in the
-<a href="https://db.apache.org/derby/docs/10.15/publishedapi/index.html">javadoc</a>
-for the 10.15 public API.
-</li>
-
-</ul>
-
 <p>
 New users should consult the
 <a href="https://db.apache.org/derby/manuals/index.html#docs_10.15">10.15 documentation</a>,
@@ -114,20 +105,6 @@ especially the
 <a href="https://db.apache.org/derby/docs/10.15/getstart/index.html">Getting Started With Derby</a> guide.
 </p>
 
-<p>
-Existing users who want to continue running Derby with a classpath should read the extended release note for issue DERBY-6945 (see below).
-</p>
-
-<p>
-Existing users who want to run Derby with a module path should consult the module diagrams in the
-<a href="https://db.apache.org/derby/docs/10.15/publishedapi/index.html">javadoc</a>
-for the 10.15 public API. Templates for wiring together a module path can be found in the
-<i>setEmbeddedCP</i>, <i>setNetworkServerCP</i>, and <i>setNetworkClientCP</i> scripts located
-in the bin directory of the release distributions, as described by the
-"Manually setting the CLASSPATH/MODULEPATH environment variables" topic in the
-<a href="https://db.apache.org/derby/docs/10.15/getstart/index.html">Getting Started With Derby</a> guide.
-</p>
-
 </newFeatures>
 
 <!--