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 2019/01/16 01:20:32 UTC

svn commit: r1851414 - /db/derby/code/branches/10.15/RELEASE-NOTES.html

Author: rhillegas
Date: Wed Jan 16 01:20:31 2019
New Revision: 1851414

URL: http://svn.apache.org/viewvc?rev=1851414&view=rev
Log:
DERBY-7010: Update release notes for the 10.15.1.1 candidate; commit derby-7010-08-aa-releaseNotesFor10.15.1.1.diff.

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

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=1851414&r1=1851413&r2=1851414&view=diff
==============================================================================
--- db/derby/code/branches/10.15/RELEASE-NOTES.html (original)
+++ db/derby/code/branches/10.15/RELEASE-NOTES.html Wed Jan 16 01:20:31 2019
@@ -1,10 +1,10 @@
 <html lang="en">
-<title>Release Notes for Apache Derby 10.15.1.0</title>
+<title>Release Notes for Apache Derby 10.15.1.1</title>
 <body>
 <h1>
-<a name="Release Notes for Apache Derby 10.15.1.0"></a>Release Notes for Apache Derby 10.15.1.0</h1>
+<a name="Release Notes for Apache Derby 10.15.1.1"></a>Release Notes for Apache Derby 10.15.1.1</h1>
 <div>
-<p>These notes describe the difference between Apache Derby release 10.15.1.0 and the preceding release 10.14.2.0.</p>
+<p>These notes describe the difference between Apache Derby release 10.15.1.1 and the preceding release 10.14.2.0.</p>
 </div>
 <ul>
 <li>
@@ -120,7 +120,7 @@ in the bin directory of the release dist
 <h2>
 <a name="Bug Fixes"></a>Bug Fixes</h2>
 <div>
-<p>The following issues are addressed by Derby release 10.15.1.0. 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.1.1. These issues are not addressed in the preceding 10.14.2.0 release.</p>
 <table border="2">
 <tr>
 <th>
@@ -167,7 +167,7 @@ JPMS components.
 </span></a>
 </li>
 </ul>
-<p>Compared with the previous release (10.14.2.0), Derby release 10.15.1.0 introduces the following new features and incompatibilities. These merit your special attention.</p>
+<p>Compared with the previous release (10.14.2.0), Derby release 10.15.1.1 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>
@@ -216,13 +216,13 @@ DataSources.
 
 
 <p>
-More privileges must be granted to the Derby jar files when running
+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 modulepath
+Derby jar files can now be wired into a module path
 for use by module-aware applications.
 </p>
 
@@ -317,22 +317,29 @@ Then adjust your application's classpath
  
 <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>.</li>
+ 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>.</li>
+ 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 additional privileges to
-Derby jar files. For more information, see the "Configuring Java
-Security" topic in the
-<a href="http://db.apache.org/derby/docs/10.15/security/index.html"><i>Derby Security Guide</i></a>
-and consult
+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="http://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>
@@ -364,7 +371,7 @@ in the <i>demo/templates</i> directory o
 <h2>
 <a name="Build Environment"></a>Build Environment</h2>
 <div>
-<p>Derby release 10.15.1.0 was built using the following environment:</p>
+<p>Derby release 10.15.1.1 was built using the following environment:</p>
 <ul>
 <li>
 <b>Branch</b> - Source code came from the 10.15 branch.</li>