Since JG 2.5 has better concurrency than 2.4 we need to test with it to
ensure it doesn't highlight areas of JBM code that didn't need to be
thread-safe before, but now do.
I believe Clebert gave the JBM test suite a spin with JG 2.5 while I was
on hols, and several tests failed that do not fail with 2.4.
Apart from that, I don't see any other issues.
Brian Stansberry wrote:
Bela Ban wrote:
> Dimitris Andreadis wrote:
>> - JGroups. It's still questionable at this point if we can move to
>> v2.5 (from 2.4.1.SP3) due to the JBoss Messaging dependency
> Why ? 2.5 is backward compatible, so JBoss Messaging should have no
> issues with this, even if they use 2.5 as a better 2.4. Tim, can you
> comment ?
>
> I strongly recommend 2.5 for inclusion, or else we'll have to wait
> until JBoss 6 to include it. Customers would upgrade to 2.5
> independently, causing headaches for the support team.
>
Clebert and I were discussing this last week, and JBM being able to
declare compatibility w/ 2.5 was looking fine.
Clebert, has anything changed on this?
--
Tim Fox
Messaging lead
JBoss - a division of Red Hat