[jboss-dev] Releasing JBoss 4 with the latest versions of AOP, Remoting, Serialization, etc.

[Ovidiu Feodorov]

OK. This is relatively easy to be implemented.

We actually already have this as part of our smoke test suite. It works 
as follows: A client using the current release libraries runs a complete 
set of tests by calling into all old servers for which we need to 
guarantee compatibility, and vice versa, a current server is being 
called into by old clients. It's pretty effective.



Scott M Stark wrote:
> No. I'm saying the backward compatibility tests need to be covering 
> any new client side dependencies jboss messaging is bringing in (aop, 
> remoting).
>
> Ovidiu Feodorov wrote:
>>
>>> . The existing messaging compatibility tests would need to be 
>>> updated to ensure there are no jbossmq dependencies as well as 
>>> expanded to pickup any leakage of these dependencies on the client 
>>> side.
>>
>> This is a completely different issue, isn't it? JBossMQ has nothing 
>> to do with these dependencies. This last issue you raised is the 
>> subject of http://jira.jboss.org/jira/browse/JBMESSAGING-553 Richard 
>> is working on it, he's very close to getting it done.
>
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
>