What are the other 3 known compliance issues? 3.2 and head should be in synch on class loaders and I need to merge some of the changes made to the jmx layer so I want to get these test working before doing the merge.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Juha Lindfors Sent: Tuesday, January 20, 2004 10:49 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] jmx unit tests the jmx module unit tests are the ones we run against, the ones in testsuite were never maintained. At least 3 of the 4 failures on compliance are known issues (and reported as such), I don't know about the JMX 1.2 notification emitter one. The two errors are both related to classloading, at least at some point the loader repository impl. in 3.2 worked correctly with these, whatever the diffs in classloading were were not ported back to head. The error in head implementation tests is new, and looks like is related to classloading again. The failure is a known issue and reported as such. I haven't run the serialization tests, Adrian will know about those. I haven't run these against 3.2 for a long while, the number of failures seems high. Serialization-1.0 full failure seems to indicate it's not running against JMX 1.0 -- Juha ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
