RE: [JBoss-dev] Jboss-mx errors

2003-02-21 Thread Jeff Haynie 
Title: Message



OK, 
this is fixed.

  
  -Original Message-From: 
  [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED] On Behalf Of 
  Jeff HaynieSent: Friday, February 21, 2003 12:54 
  PMTo: [EMAIL PROTECTED]Subject: 
  RE: [JBoss-dev] Jboss-mx errors
  i 
  did a brand new checkout into a clean directory.
   
  i'll 
  fix the build.
   
  thanks,
  

-Original Message-From: 
[EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of 
Bill BurkeSent: Friday, February 21, 2003 12:49 
PMTo: [EMAIL PROTECTED]Subject: 
RE: [JBoss-dev] Jboss-mx errors
jmx/build.xml probably needs to reference dom4j.jar.  I just 
check out last night at 10 pm with no problems.  Did you do an update 
instead of a clean checkout?  I don't think update grabs thirdparty 
jars for some reason.

  -Original Message-From: 
  [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED]On Behalf Of 
  Jeff HaynieSent: Friday, February 21, 2003 12:43 
  PMTo: [EMAIL PROTECTED]Subject: 
      [JBoss-dev] Jboss-mx errors
  I'm getting a bunch of these errors while 
  building fresh checkout of jboss-mx from HEAD. Anyone have any 
  ideas?
   
  [execmodules] 
  C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:37: 
  package org.dom4j does not exist[execmodules] import 
  org.dom4j.Document;[execmodules]  
  ^[execmodules] 
  C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:38: 
  package org.dom4j does not exist[execmodules] import 
  org.dom4j.DocumentException;[execmodules]  
  ^[execmodules] 
  C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:39: 
  package org.dom4j does not exist[execmodules] import 
  org.dom4j.Element;[execmodules]  
  ^[execmodules] 
  C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:40: 
  package org.dom4j.iodoes not exist[execmodules] import 
  org.dom4j.io.SAXReader;[execmodules] 
  ^[execmodules] 
  C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:63: 
  cannot resolve symbol
   
  [execmodules] symbol  : class 
  Element[execmodules] location: class 
  org.jboss.mx.metadata.JBossXMBean10[execmodules]    
  private Element 
  element;[execmodules]    
  ^[execmodules] 
  C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:78: 
  cannot resolve symbol
   
  [execmodules] symbol  : class 
  Element[execmodules] location: class 
  org.jboss.mx.metadata.JBossXMBean10[execmodules]    
  public JBossXMBean10(String mmbClassName, String resourceClassName, 
  Element element, Map 
  properties)[execmodules]    
  ^[execmodules] 
  C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:127: 
  cannot resolve symbol[execmodules] symbol  : class 
  Element[execmodules] location: class 
  org.jboss.mx.metadata.JBossXMBean10[execmodules]    
  protected Descriptor getDescriptor(final Element parent, final String 
  infoName, final String type) throws 
  NotCompliantMBeanException[execmodules] 
  ^[execmodules] 
  C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean12.java:9: 
  package org.dom4j does not exist[execmodules] import 
  org.dom4j.Attribute;[execmodules]  
  ^[execmodules] 
  C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean12.java:10: 
  package org.dom4j 
doe

RE: [JBoss-dev] Jboss-mx errors

2003-02-21 Thread Jeff Haynie 
Title: Message



i did 
a brand new checkout into a clean directory.
 
i'll 
fix the build.
 
thanks,

  
  -Original Message-From: 
  [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED] On Behalf Of 
  Bill BurkeSent: Friday, February 21, 2003 12:49 
  PMTo: [EMAIL PROTECTED]Subject: 
  RE: [JBoss-dev] Jboss-mx errors
  jmx/build.xml probably needs to reference dom4j.jar.  I just check 
  out last night at 10 pm with no problems.  Did you do an update instead 
  of a clean checkout?  I don't think update grabs thirdparty jars for some 
  reason.
  
-Original Message-From: 
[EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED]On Behalf Of 
Jeff HaynieSent: Friday, February 21, 2003 12:43 
PMTo: [EMAIL PROTECTED]Subject: 
    [JBoss-dev] Jboss-mx errors
I'm getting a bunch of these errors while 
building fresh checkout of jboss-mx from HEAD. Anyone have any 
ideas?
 
[execmodules] 
C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:37: 
package org.dom4j does not exist[execmodules] import 
org.dom4j.Document;[execmodules]  
^[execmodules] 
C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:38: 
package org.dom4j does not exist[execmodules] import 
org.dom4j.DocumentException;[execmodules]  
^[execmodules] 
C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:39: 
package org.dom4j does not exist[execmodules] import 
org.dom4j.Element;[execmodules]  
^[execmodules] 
C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:40: 
package org.dom4j.iodoes not exist[execmodules] import 
org.dom4j.io.SAXReader;[execmodules] 
^[execmodules] 
C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:63: 
cannot resolve symbol
 
[execmodules] symbol  : class 
Element[execmodules] location: class 
org.jboss.mx.metadata.JBossXMBean10[execmodules]    
private Element 
element;[execmodules]    
^[execmodules] 
C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:78: 
cannot resolve symbol
 
[execmodules] symbol  : class 
Element[execmodules] location: class 
org.jboss.mx.metadata.JBossXMBean10[execmodules]    
public JBossXMBean10(String mmbClassName, String resourceClassName, Element 
element, Map 
properties)[execmodules]    
^[execmodules] 
C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:127: 
cannot resolve symbol[execmodules] symbol  : class 
Element[execmodules] location: class 
org.jboss.mx.metadata.JBossXMBean10[execmodules]    
protected Descriptor getDescriptor(final Element parent, final String 
infoName, final String type) throws 
NotCompliantMBeanException[execmodules] 
^[execmodules] 
C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean12.java:9: 
package org.dom4j does not exist[execmodules] import 
org.dom4j.Attribute;[execmodules]  
^[execmodules] 
C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean12.java:10: 
package org.dom4j doe

RE: [JBoss-dev] Jboss-mx errors

2003-02-21 Thread Bill Burke 



jmx/build.xml probably needs to reference dom4j.jar.  I just check 
out last night at 10 pm with no problems.  Did you do an update instead of 
a clean checkout?  I don't think update grabs thirdparty jars for some 
reason.

  -Original Message-From: 
  [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED]On Behalf Of Jeff 
  HaynieSent: Friday, February 21, 2003 12:43 PMTo: 
  [EMAIL PROTECTED]Subject: [JBoss-dev] Jboss-mx 
  errors
  I'm getting a bunch of these errors while 
  building fresh checkout of jboss-mx from HEAD. Anyone have any 
  ideas?
   
  [execmodules] 
  C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:37: 
  package org.dom4j does not exist[execmodules] import 
  org.dom4j.Document;[execmodules]  
  ^[execmodules] 
  C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:38: 
  package org.dom4j does not exist[execmodules] import 
  org.dom4j.DocumentException;[execmodules]  
  ^[execmodules] 
  C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:39: 
  package org.dom4j does not exist[execmodules] import 
  org.dom4j.Element;[execmodules]  
  ^[execmodules] 
  C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:40: 
  package org.dom4j.iodoes not exist[execmodules] import 
  org.dom4j.io.SAXReader;[execmodules] 
  ^[execmodules] 
  C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:63: 
  cannot resolve symbol
   
  [execmodules] symbol  : class 
  Element[execmodules] location: class 
  org.jboss.mx.metadata.JBossXMBean10[execmodules]    private 
  Element 
  element;[execmodules]    
  ^[execmodules] 
  C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:78: 
  cannot resolve symbol
   
  [execmodules] symbol  : class 
  Element[execmodules] location: class 
  org.jboss.mx.metadata.JBossXMBean10[execmodules]    public 
  JBossXMBean10(String mmbClassName, String resourceClassName, Element element, 
  Map 
  properties)[execmodules]    
  ^[execmodules] 
  C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:127: 
  cannot resolve symbol[execmodules] symbol  : class 
  Element[execmodules] location: class 
  org.jboss.mx.metadata.JBossXMBean10[execmodules]    
  protected Descriptor getDescriptor(final Element parent, final String 
  infoName, final String type) throws 
  NotCompliantMBeanException[execmodules] 
  ^[execmodules] 
  C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean12.java:9: 
  package org.dom4j does not exist[execmodules] import 
  org.dom4j.Attribute;[execmodules]  
  ^[execmodules] 
  C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean12.java:10: 
  package org.dom4j doe

[JBoss-dev] Jboss-mx errors

2003-02-21 Thread Jeff Haynie 



I'm getting a bunch of these errors while building 
fresh checkout of jboss-mx from HEAD. Anyone have any ideas?
 
[execmodules] 
C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:37: 
package org.dom4j does not exist[execmodules] import 
org.dom4j.Document;[execmodules]  
^[execmodules] 
C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:38: 
package org.dom4j does not exist[execmodules] import 
org.dom4j.DocumentException;[execmodules]  
^[execmodules] 
C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:39: 
package org.dom4j does not exist[execmodules] import 
org.dom4j.Element;[execmodules]  
^[execmodules] 
C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:40: 
package org.dom4j.iodoes not exist[execmodules] import 
org.dom4j.io.SAXReader;[execmodules] 
^[execmodules] 
C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:63: 
cannot resolve symbol
 
[execmodules] symbol  : class 
Element[execmodules] location: class 
org.jboss.mx.metadata.JBossXMBean10[execmodules]    private 
Element 
element;[execmodules]    
^[execmodules] 
C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:78: 
cannot resolve symbol
 
[execmodules] symbol  : class 
Element[execmodules] location: class 
org.jboss.mx.metadata.JBossXMBean10[execmodules]    public 
JBossXMBean10(String mmbClassName, String resourceClassName, Element element, 
Map 
properties)[execmodules]    
^[execmodules] 
C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean10.java:127: 
cannot resolve symbol[execmodules] symbol  : class 
Element[execmodules] location: class 
org.jboss.mx.metadata.JBossXMBean10[execmodules]    protected 
Descriptor getDescriptor(final Element parent, final String infoName, final 
String type) throws 
NotCompliantMBeanException[execmodules] 
^[execmodules] 
C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean12.java:9: 
package org.dom4j does not exist[execmodules] import 
org.dom4j.Attribute;[execmodules]  
^[execmodules] 
C:\cvs-jboss-head\jboss-mx\jmx\src\main\org\jboss\mx\metadata\JBossXMBean12.java:10: 
package org.dom4j doe