Hi, Nope I'm not missing anything :) I'm saying keep the integration tests as it is (I'm talking about the security tests in the integration module) and they can run having rampart as an external dependancy. That's it. You don't want to move them anywhere. If Axis2 code is not compatible with the latest rampart build (which now comes as an external dependancy), Axis2 build will fail! In my mind Axis2 integration tests belong in Axis2 and not anywhere else. We do have XMLBeans and Jibx tests that way.
Ajith On 9/1/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
Ajith Ranabahu wrote: > Hi, > I'm also +1 on this move - it makes things modular and easy to handle. > BTW I don't think you need to move the integration tests - they are > *Axis2* integration tests and they should not go to any other project! No, you miss something here Ajith. They are not mere integration tests. They test how Rahas or Rampart or whatever works hand-in-hand. But that includes Axis2 integration tests as well. Thats the reason behind me mentioning that we need some test cases to test the integration to compensate the removal of Security integration tests. Read point #2 my earlier mail. -- Chinthaka
-- Ajith Ranabahu --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
