The problem is caused because JBossMX has only just been added to the main build, but the testsuite only recompiles itself. If you "cvs update" and don't "build" before "build run-testsuite" you get errors.
I believe the hourly compile was turned off a weeks ago, so the Automated Testsuite hasn't got a jboss-jmx.jar. Regards, Adrian >From: Juha-P Lindfors <[EMAIL PROTECTED]> >To: Adrian Brock <[EMAIL PROTECTED]> >CC: Trevor Squires <[EMAIL PROTECTED]>, Tom Elrod ><[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> >Subject: Re: testsuite and standalone jboss-mx module >Date: Sun, 3 Feb 2002 13:40:43 +0200 (EET) > > >Hi guys, > >I agree on the criticism on integrating the JBossMX tests to the main >suite. As it stands, it doesn't make much sense. It is slow and bloated >(I never get past the MQ tests, it just seems to hang there but even >running only the JBossMX tests seems quite a bit slower (from 6 >seconds to 36 seconds on my laptop). We want it fast and lean so people >can really run the suite easily after each and every compile (I, like >Trevor, am used to running it all the time as well). > >For now, I suggest you keep updating only the tests in the jmx module (or >go with the jbossmx-test module idea if you still have the energy). >However, the JBossMX Test integration is right now stopping other people >from running their testsuites and needs to be fixed. I can't reproduce the >problem (I get stuck in the MQ tests) but will try to find the cause. >Adrian, can you look into it as well as soon as possible. > >Thanks, > >-- Juha > > > >-- >Juha Lindfors >Author of "JMX: Managing J2EE with Java Management Extensions" >Senior Developer, JBoss Group LLC > > > _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
