Re: svn commit: r647361 - /geronimo/server/branches/2.1/pom.xml

[Donald Woods]

Is there a reason you only updated wadi-aop to 2.0-M10 and not the rest of the WADI artifacts?

-Donald


Gianny Damour wrote:

Hello Joe,





Thanks,
Gianny

On 12/04/2008, at 1:56 PM, Joe Bohn wrote:

It is a change intended for the 2.1 branch as I would like G 2.1.1 to use WADI 2.0-M10. It fixes a replication bug: the dirty flag of a session is reset when a null value is retrieved from a session. As a consequence, session state updates are not pushed to replication peers upon completion of request handling. Hence, sessions recovered from replication servers following a peer crash may not reflect the latest state.

Gianny,



Thanks,
Joe


[EMAIL PROTECTED] wrote:

Was this change perhaps intended for trunk rather than branches/2.1 given that 2.0-M10 was just released a few days ago? If you did intend it for 2.1, can you provide some more information on why it is necessary? We are nearly ready to branch for 2.1.1 and I'm trying to keep the changes in the 2.1 branch to an absolute minimum.

Author: gdamour
Date: Fri Apr 11 18:24:12 2008
New Revision: 647361
URL: http://svn.apache.org/viewvc?rev=647361&view=rev
Log:
upgrade to 2.0-M10
Modified:
    geronimo/server/branches/2.1/pom.xml
Modified: geronimo/server/branches/2.1/pom.xml

URL: http://svn.apache.org/viewvc/geronimo/server/branches/2.1/pom.xml?rev=647361&r1=647360&r2=647361&view=diff ==============================================================================

--- geronimo/server/branches/2.1/pom.xml (original)
+++ geronimo/server/branches/2.1/pom.xml Fri Apr 11 18:24:12 2008
@@ -1054,7 +1054,7 @@
             <dependency>
                 <groupId>org.codehaus.wadi</groupId>
                 <artifactId>wadi-aop</artifactId>
-                <version>2.0-M9</version>
+                <version>2.0-M10</version>
             </dependency>
              <dependency>

smime.p7s
Description: S/MIME Cryptographic Signature