Doh! I see, I didn't commit common/build.xml
+1 Guiness for me, sorry.
Regards,
Adrian
From: "Adrian Brock" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] 3.2 build broken for a while
Date: Sat, 22 Mar 2003 23:32:58 +
Blo
CTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, March 22, 2003 3:32 PM
Subject: Re: [JBoss-dev] 3.2 build broken for a while
> Bloody CVS merge putting jboss.jmx back in!
>
> Why didn't common compile over Sun'
Bloody CVS merge putting jboss.jmx back in!
Why didn't common compile over Sun's RI,
it did for me?
Regards,
Adrian
From: "Scott M Stark" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
Subject: Re: [JBoss-dev] 3.2 build broken for a while
David Jencks" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, March 22, 2003 12:54 PM
Subject: Re: [JBoss-dev] 3.2 build broken for a while
> tools/etc/xdoclet/templates/mbean-custom.xdt
>
> david
---
tools/etc/xdoclet/templates/mbean-custom.xdt
david
On 2003.03.22 15:44 Scott M Stark wrote:
> The removal of the logging from jmx and switching of dependency ordering
> between common and jmx has broken the build until this is resolved. One
> complication in doing this is the fact that the xdocl
The removal of the logging from jmx and switching of dependency ordering
between common and jmx has broken the build until this is resolved. One
complication in doing this is the fact that the xdoclet generated mbeans
are referencing a org.jboss.util.jmx.ObjectNameFactory:
public static final java
