Those are the details I have been trying to avoid for now by converting the existing jruby integration test code into a Maven plugin. We can slowly take that complexity apart a piece at a time even after conversion to Maven is complete. Doing it all upfront would take too long :(
Thanks; Eric On 6/1/07, Eugene Kuleshov <[EMAIL PROTECTED]> wrote:
Eric Redmond wrote: > On a more general note - the tcbuild plugin is only used for running > integration tests... when i get the "mvn test" stuff working and > checked in, each project will compile/unit test via their respective > JDKs (no more profile-based compilation). BTW, Eric, not sure if you know that, but we need to be able to run certain unit tests on Sun's 1.4 - 1.6 and IBM's JVM's (1.5 only). General rule, if project has 1.4 level, tests are running on 1.4 1.5 and 1.6, and if it has 1.5 level - it runs on 1.5 and 1.6, etc. Tests for spring modules need to run with different versions of Spring (usually latest 1.2.x and 2.x) In-container tests runs on variety of containers - Tomcat 5.0, 5.5, etc, Jetty, Weblogic 8.1, and few others regards, Eugene
-- Eric Redmond http://www.sonatype.com
_______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
