Thanks for the suggestions. I did look at the invoker plugin, and see you can set up separate maven "builds" at different versions.
I guess what I'm still missing is how to write one test that (ideally, within one JVM) starts a "server" running with version 2.4.0 of some artifacts, and then runs a "client" having the same artifacts but at version 2.4.2, in the same JVM (I'm thinking, using class loader stuff), run through its tests - connecting to the service, sending messages, receiving, etc. We already have test cases that do this, but of course, the server and the client are at the same version level. An approach I am considering, is giving up on running within one JVM, and having the test do a Java exec call with a class path set up somehow to point to version 2.4.0 (for example). I'm not sure how to reference that version via maven artifact mechanisms, when the rest of the test would be referencing those same artifacts at a different version... -Marshall On 11/12/2013 10:20 AM, Stephen Connolly wrote: > Maven invoker plugin would be one way to do that. > > Basically you have a "child" project for each touchstone version... or you > can use invoker.properties to pass the touchstone versions through to the > executions > > > On 12 November 2013 15:15, Marshall Schor <[email protected]> wrote: > >> Hi, >> >> We would like to run tests that test for compatibility between newer >> releases >> and older versions, for a "client-server" kind of application. The main >> idea >> here is that the tests would be run with the client running one version of >> things, and the server running another. >> >> Is there a suggested approach for doing this using Maven? The main issue >> I see >> is that the test case would depend on multiple versions of the same >> artifacts - >> some version being "assigned" to the client, and some to the server. But I >> don't think Maven allows that? >> >> It would be good to hear from others who have previously faced down this >> kind of >> issue :-) >> >> -Marshall Schor >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
