I think we want something along the lines of: % maven local Run the local build and unit tests (no network connection required, but includes local server tests)
% maven all Run the above plus some tests which check basic interop against remote server(s) % maven interop Run the above plus a larger interop suite against multiple servers It would be extra nice if we could have a switch which enables auto-detection of "local/all". I.e. by default if I "maven" with no arguments, I could select a) local, b) all, or c) test network connection and run all if it's there and local if not. Thoughts? --Glen > -----Original Message----- > From: Davanum Srinivas [mailto:[EMAIL PROTECTED] > Sent: Friday, July 15, 2005 11:06 AM > To: [email protected]; Thilina Gunarathne > Subject: Re: [Axis2] Need to have a Reliable way to run MTOM > test cases.... > > Thilina, > > best way to do this is to get patches to geronimo. Could u spend say > 30 mins and let me know? we need to get geronimo fixes in ASAP. > > -- dims > > On 7/15/05, Thilina Gunarathne <[EMAIL PROTECTED]> wrote: > > Hi all, > > Today when i tried to run the MTOM test cases I found out > that they are > > failing and MTOM is not working :( . I know this is > unavoidable with the > > changes we are doing to other modules, unless we have a way > to test MTOM. > > > > I think it's better If we can come up with a way to run > MTOM test cases > > whenever we are doing a commit. (For the moment MTOM test > cases have been > > excluded due to unavailability of JavaMail & Activation). > A separate maven > > goal, for which we guarantee to the presence of java mail & > activation, will > > be a fine solution for this. If not we'll continuously face > this problem... > > > > Devs, > > Till we have a mechanism to test MTOM pls be carefull with ur > > changes.......Specially OM and Transport packages.. > > > > ~Thilina > > > > -- > > "May the SourcE be with u" > > http://www.bloglines.com/blog/thilina > > > -- > Davanum Srinivas -http://blogs.cocoondev.org/dims/ > >
