[jboss-cvs] JBoss Messaging SVN: r3846 - branches/Branch_JBossMessaging_1_4_0_SP3_CP/docs.

Thu Mar 6 03:36:19 EST 2008

Author: timfox
Date: 2008-03-06 03:36:19 -0500 (Thu, 06 Mar 2008)
New Revision: 3846

Modified:
   branches/Branch_JBossMessaging_1_4_0_SP3_CP/docs/README.html
Log:
http://jira.jboss.org/jira/browse/JBMESSAGING-1204


Modified: branches/Branch_JBossMessaging_1_4_0_SP3_CP/docs/README.html
===================================================================

--- branches/Branch_JBossMessaging_1_4_0_SP3_CP/docs/README.html	2008-03-05 15:07:24 UTC (rev 3845)
+++ branches/Branch_JBossMessaging_1_4_0_SP3_CP/docs/README.html	2008-03-06 08:36:19 UTC (rev 3846)
@@ -3,44 +3,31 @@
 <head>
   <meta content="text/html; charset=ISO-8859-1"
  http-equiv="content-type">
-  <title>JBoss Messaging 1.4.0.SP3 Release Notes</title>
+  <title>JBoss Messaging 1.4.0.SP3_CP02 Release Notes</title>
 </head>
 <body>
 
-<h1>Release Notes - JBoss Messaging - Version 1.4.0.SP3</h1>
+<h1>Release Notes - JBoss Messaging - Version 1.4.0.SP3_CP02</h1>
 
 <br>
 
 <h2>13 December 2007</h2>
 
-These are the release notes for JBoss Messaging 1.4.0 Service Pack 3 (SP3).<br><br>
+These are the release notes for JBoss Messaging 1.4.0 Service Pack 3 (SP3) CP02<br><br>
 
 For full description of the contents please see the JBoss Messaging project JIRA.<br><br>
 
-When upgrading an existing installation be sure to update all the configuration files in server/<server name>/deploy/jboss-messaging.sar with the newer versions and replace jboss-messaging.jar in server/<server name>/lib and on the client classpath. You will also need to drop all tables and indexes in the database.<br><br>
+When upgrading an existing installation be sure to update all the configuration files in server/&lt;server name&gt;/deploy/jboss-messaging.sar with the newer versions and replace jboss-messaging.jar in server/&lt;server name&gt;/lib and on the client classpath. You will also need to drop all tables and indexes in the database.<br><br>
 
-This release of JBoss Messaging also requires a patched JBoss Remoting jar. The required version is 2.2.2.SP4. Be sure that server/<server name>/lib contains this jar and that it is also present as the first entry on the client classpath. This is critical to ensure proper operation of JBoss Messaging 1.4.0.SP3!<br><br>
+This release of JBoss Messaging also requires a patched JBoss Remoting jar. The required version is 2.2.2.SP5. Be sure that server/&lt;server name&gt;/lib contains this jar and that it is also present as the first entry on the client classpath. This is critical to ensure proper operation of JBoss Messaging 1.4.0.SP3!<br><br>
 
 Enjoy!<br><br>
 
 
+Release Notes - JBoss Messaging - Version 1.4.0.SP3_CP02
 
 
-Release Notes - JBoss Messaging - Version 1.4.0.SP3
 
-<h2>Bug</h2>
-<ul>
-<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1200'>JBMESSAGING-1200</a>] - Session.executor is leaking the first classLoader used</li>
-</ul>
-
-<h2>Task</h2>
-<ul>
-<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1188'>JBMESSAGING-1188</a>] - Workaround for JBMREM-845</li>
-<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1199'>JBMESSAGING-1199</a>] - Improvements to consumer flow control</li>
-</ul>
-
-
-
 </body>
 </html>
 


