[jboss-cvs] JBoss Messaging SVN: r3847 - branches/Branch_Stable/docs.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Mar 6 03:36:46 EST 2008
Author: timfox
Date: 2008-03-06 03:36:46 -0500 (Thu, 06 Mar 2008)
New Revision: 3847
Modified:
branches/Branch_Stable/docs/README.html
Log:
http://jira.jboss.org/jira/browse/JBMESSAGING-1204
Modified: branches/Branch_Stable/docs/README.html
===================================================================
--- branches/Branch_Stable/docs/README.html 2008-03-06 08:36:19 UTC (rev 3846)
+++ branches/Branch_Stable/docs/README.html 2008-03-06 08:36:46 UTC (rev 3847)
@@ -3,45 +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.1.beta2 Release Notes</title>
</head>
<body>
-<h1>Release Notes - JBoss Messaging - Version 1.4.1.Beta1</h1>
+<h1>Release Notes - JBoss Messaging - Version 1.4.1.beta2</h1>
<br>
-<h2>23 January 2008</h2>
+<h2>13 December 2007</h2>
-These are the release notes for JBoss Messaging 1.4.1 Betta1).<br><br>
+These are the release notes for JBoss Messaging 1.4.1.beta2<br><br>
-This release was created mainly to allow JBoss AS 5 needs, as JBoss AS 5 needs to change few options on Security as the pluggable security API has changed.
+For full description of the contents please see the JBoss Messaging project JIRA.<br><br>
-For the 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>
-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/<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!<br><br>
Enjoy!<br><br>
+Release Notes - JBoss Messaging - Version 1.4.1.beta2
-Release Notes - JBoss Messaging - Version 1.4.1.beta1
-
-<h2>Bug</h2>
-<ul>
-<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1216'>JBMESSAGING-1216</a>] - getJMSDestination() is returning an incorrect object type after a message has been delivered.</li>
-<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1221'>JBMESSAGING-1221</a>] - Memory Leak in MessagingXAResource</li>
-</ul>
-
-<h2>Feature Request</h2>
-<ul>
-<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1223'>JBMESSAGING-1223</a>] - Make SecurityStore Configurable</li>
-</ul>
-
</body>
</html>
More information about the jboss-cvs-commits
mailing list