On Friday 23 July 2010 4:52:41 pm Benson Margulies wrote: > In the branch where we're working on jetty 7, I've started to set up > the use of the new-ish 'failsafe' plugin to run integrations tests. > > It occurs to me that we could probably use this to include all the > samples in the build. > > Rough proposal: > > 1: we want to run builds on the samples with cxf.version set > appropriately. I think that we can use a slew of ../.. in module > pathnames to accomplish this, except that I don't see how to get the > right -D environment into there. Ironically, maven -> ant -> maven > looks possible. There must be some way to get one maven run to launch > another one with arbitrary arguments -- I suppose a new mojo is a > possible solution here.
If they are part of the "release/deploy" build as well, then we could get rid of the cxf.version variable in there and have the <version> set to the same 2.3.0-SNAPSHOT as the rest of the build. The release plugin would replace the version in there as part of the release process. This would actually solve one of the JIRA's about this issue where running a sample from the 2.2.8 kit actually download 2.2.9 (or even a snapshot). Having the release process set the right version is probably a good thing. One thing I would suggest, however, is to turn off the deploy plugin. I don't see much point wasting time/bandwidth deploying these. > 2: for each sample, there's some sort of server and then some sort of > client. We can at least launch the server, launch the client, and > verify that nothing explodes. Something to experiment with I suppose. :-) -- Daniel Kulp dk...@apache.org http://dankulp.com/blog
