I've fixed most of the testsuite, there are still two
modelmbean failures I don't understand.
The descriptor validation part of the spec is voodoo to me.
build test-compliance-JBossMX
Also, I fixed some of the tests to catch the RuntimeOperationsException
thrown by Descriptor.isValid()
But the JM
AM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] Why the two jboss logging frameworks?
>
> I'll fix it in both 3.2 and head
> My fault for not keeping head in line.
>
> Regards,
> Adrian
>
---
This SF.Net email
Thomas or Tom,
A lot of the JMX testsuite tests for JBossMX are failing.
Either the tests should be fixed or the reason why they
fail analysed.
Last time I ran it, there were three "known issues"
non of them important.
Regards,
Adrian
On Sat, 2004-04-17 at 14:00, Adrian Brock wrote:
> I'll fix i
I'll fix it in both 3.2 and head
My fault for not keeping head in line.
Regards,
Adrian
On Sat, 2004-04-17 at 13:42, Adrian Brock wrote:
> The JMX logging framework was removed from 3.2.0 but never
> from head. When Tom backported jmx from head into 3.2.4RC1
> he also copied the old jmx logging f
The JMX logging framework was removed from 3.2.0 but never
from head. When Tom backported jmx from head into 3.2.4RC1
he also copied the old jmx logging framework.
Regards,
Adrian
On Sat, 2004-04-17 at 13:25, Scott M Stark wrote:
> In trying to cleanup the logging for bug [ 936465 ] JCA layer has
In trying to cleanup the logging for bug [ 936465 ] JCA layer has
invalid assumption about Log4jLoggerPlugin
https://sourceforge.net/tracker/index.php?func=detail&aid=936465&group_i
d=22866&atid=376685
I see that we have two seperate frameworks:
jmx org.jboss.mx.logging
comon org.jboss.logging
