I have been struggling with this for another project, too. Ideally, it would be great to have a "continuous integration" build that would also deploy and test the app(s) in a bunch of containers automatically. You'd still have to install and configure some deployment details, of course, but it would be nice to have a machine with a bunch of containers on it that would run and test builds in all of them automatically. I imagine the same system could be used to deploy to a developer's favorite container or containers for local testing on a much smaller scale.
Are there any projects out there intended to make it easier to test the same app(s) in a variety of containers? -Max ----- Original Message ----- From: "Ted Husted" <[EMAIL PROTECTED]> To: "Struts Developers List" <[EMAIL PROTECTED]> Sent: Friday, June 06, 2003 3:39 PM Subject: Re: Status check? > Martin Cooper wrote: > > For the main Struts release, the most time-consuming part is just testing > > that everything works with all the supported containers (including all the > > web apps). > > So, I take it we would be satisfied with testing our sample applications > against the binary distribution (rather than against all the > permutations of Java 1.2, 1.3, 1.4, and Servlet 2.2 and 2.3). > > And then for Cactus, I take it we would run TC 3.3 against Servlet 2.2, > and TC 4.x against Servlet 2.3, as that would be the expected use. > > -Ted. > > > > --------------------------------------------------------------------- > 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]
