Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
Hi, Yep - tried with and without... but you'd think it would be consistent if that was the problem - ant would either have enough memory or not... Thanks, Chris --- Stephen Coy <[EMAIL PROTECTED]> wrote: > Have you tried the equivalent of this sort of thing in your script? > > [EMAIL PROTECTED] jboss-3.2]$ ANT_OPTS="-Xmx256M" build/build.sh > > Steve Coy > > On Wednesday, March 26, 2003, at 01:11 AM, Chris Kimpton wrote: > > > > > --- Chris Kimpton <[EMAIL PROTECTED]> wrote: > >> Hi, > >> > >> Does anyone get problems compiling HEAD on Linux - > >> > >>> Caused by: java.lang.OutOfMemoryError > >> > >> Within the doclet stuff... > >> > > > > This seems to be my problem - since I can compile it manually > outside > > of my scripts... but all they do is one shell script calls > another > > script which calls build.sh... Is there some default "sh" memory > > limits that are limiting things? > > > > I will look at getting a windows version running and probably > > re-writing my scripts since they are getting out of hand... > > > > But basically - the regular compiles are currently stopped! > > > > Chris > > > > --- > This SF.net email is sponsored by: > The Definitive IT and Networking Event. Be There! > NetWorld+Interop Las Vegas 2003 -- Register today! > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development = __ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.com --- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
Have you tried the equivalent of this sort of thing in your script? [EMAIL PROTECTED] jboss-3.2]$ ANT_OPTS="-Xmx256M" build/build.sh Steve Coy On Wednesday, March 26, 2003, at 01:11 AM, Chris Kimpton wrote: --- Chris Kimpton <[EMAIL PROTECTED]> wrote: Hi, Does anyone get problems compiling HEAD on Linux - Caused by: java.lang.OutOfMemoryError Within the doclet stuff... This seems to be my problem - since I can compile it manually outside of my scripts... but all they do is one shell script calls another script which calls build.sh... Is there some default "sh" memory limits that are limiting things? I will look at getting a windows version running and probably re-writing my scripts since they are getting out of hand... But basically - the regular compiles are currently stopped! Chris --- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
--- Chris Kimpton <[EMAIL PROTECTED]> wrote: > Hi, > > Does anyone get problems compiling HEAD on Linux - > > > Caused by: java.lang.OutOfMemoryError > > Within the doclet stuff... > This seems to be my problem - since I can compile it manually outside of my scripts... but all they do is one shell script calls another script which calls build.sh... Is there some default "sh" memory limits that are limiting things? I will look at getting a windows version running and probably re-writing my scripts since they are getting out of hand... But basically - the regular compiles are currently stopped! Chris = __ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.com --- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
Hi, Does anyone get problems compiling HEAD on Linux - > Caused by: java.lang.OutOfMemoryError Within the doclet stuff... Regards, Chris --- [EMAIL PROTECTED] wrote: > > = > ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR > DETAILS= > = > = __ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.com --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
I'm dumb, dumb, dumb. I checked this in in one sandbox and tested it in another. -dain On Saturday, March 15, 2003, at 11:04 AM, Dain Sundstrom wrote: What is the deal with this? It builds perfectly for me. -dain On Saturday, March 15, 2003, at 10:38 AM, [EMAIL PROTECTED] wrote: = ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS= = JAVA VERSION DETAILS java version "1.4.1_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01) Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode) = HERE ARE THE LAST 50 LINES OF THE LOG FILE getTransaction(), relatedId, myCtx.getId()); ^ /home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/plugins/ cmp/jdbc/bridge/JDBCCMRFieldBridge.java:1226: cannot resolve symbol symbol : variable container location: class org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge TransactionManager tm = container.getTransactionManager(); ^ /home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/ http/interfaces/Util.java:63: warning: com.sun.net.ssl.HttpsURLConnection in com.sun.net.ssl has been deprecated if( conn instanceof com.sun.net.ssl.HttpsURLConnection ) ^ /home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/ http/interfaces/Util.java:68: warning: com.sun.net.ssl.HttpsURLConnection in com.sun.net.ssl has been deprecated com.sun.net.ssl.HttpsURLConnection sconn = (com.sun.net.ssl.HttpsURLConnection) conn; ^ /home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/ http/interfaces/Util.java:68: warning: com.sun.net.ssl.HttpsURLConnection in com.sun.net.ssl has been deprecated com.sun.net.ssl.HttpsURLConnection sconn = (com.sun.net.ssl.HttpsURLConnection) conn; ^ /home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/ connector/rmi/RMIConnectorImpl.java:592: warning: deserialize(java.lang.String,javax.management.ObjectName,byte[]) in javax.management.MBeanServer has been deprecated public ObjectInputStream deserialize(String className, ObjectName loaderName, byte[] data) ^ /home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/ connector/rmi/RMIConnectorImpl.java:581: warning: deserialize(java.lang.String,byte[]) in javax.management.MBeanServer has been deprecated public ObjectInputStream deserialize(String className, byte[] data) ^ /home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/ connector/rmi/RMIConnectorImpl.java:570: warning: deserialize(javax.management.ObjectName,byte[]) in javax.management.MBeanServer has been deprecated public ObjectInputStream deserialize(ObjectName name, byte[] data) ^ /home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/ connector/ejb/EJBConnector.java:56: warning: deserialize(java.lang.String,javax.management.ObjectName,byte[]) in javax.management.MBeanServer has been deprecated public class EJBConnector ^ /home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/ connector/ejb/EJBConnector.java:56: warning: deserialize(java.lang.String,byte[]) in javax.management.MBeanServer has been deprecated public class EJBConnector ^ /home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/ connector/ejb/EJBConnector.java:56: warning: deserialize(javax.management.ObjectName,byte[]) in javax.management.MBeanServer has been deprecated public class EJBConnector ^ /home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/ connector/ejb/EJBConnector.java:56: warning: deserialize(java.lang.String,javax.management.ObjectName,byte[]) in javax.management.MBeanServer has been deprecated public class EJBConnector ^ /home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/ connector/ejb/EJBConnector.java:56: warning: deserialize(java.lang.String,byte[]) in javax.management.MBeanServer has been deprecated public class EJBConnector ^ /home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/ connector/ejb/EJBConnector.java:56: warning: deserialize(javax.management.ObjectName,byte[]) in javax.management.MBeanServer has been deprecated public class EJBConnector ^ 6 errors 22 warnings BUILD FAILED file:/home/jboss/jbossci/jboss-head/server/build.xml:291: Compile failed; see the compiler error output for details. Total time: 1 minute 55 seconds --- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register her
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
What is the deal with this? It builds perfectly for me. -dain On Saturday, March 15, 2003, at 10:38 AM, [EMAIL PROTECTED] wrote: = ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS= = JAVA VERSION DETAILS java version "1.4.1_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01) Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode) = HERE ARE THE LAST 50 LINES OF THE LOG FILE getTransaction(), relatedId, myCtx.getId()); ^ /home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/plugins/ cmp/jdbc/bridge/JDBCCMRFieldBridge.java:1226: cannot resolve symbol symbol : variable container location: class org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge TransactionManager tm = container.getTransactionManager(); ^ /home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/ http/interfaces/Util.java:63: warning: com.sun.net.ssl.HttpsURLConnection in com.sun.net.ssl has been deprecated if( conn instanceof com.sun.net.ssl.HttpsURLConnection ) ^ /home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/ http/interfaces/Util.java:68: warning: com.sun.net.ssl.HttpsURLConnection in com.sun.net.ssl has been deprecated com.sun.net.ssl.HttpsURLConnection sconn = (com.sun.net.ssl.HttpsURLConnection) conn; ^ /home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/ http/interfaces/Util.java:68: warning: com.sun.net.ssl.HttpsURLConnection in com.sun.net.ssl has been deprecated com.sun.net.ssl.HttpsURLConnection sconn = (com.sun.net.ssl.HttpsURLConnection) conn; ^ /home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/ connector/rmi/RMIConnectorImpl.java:592: warning: deserialize(java.lang.String,javax.management.ObjectName,byte[]) in javax.management.MBeanServer has been deprecated public ObjectInputStream deserialize(String className, ObjectName loaderName, byte[] data) ^ /home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/ connector/rmi/RMIConnectorImpl.java:581: warning: deserialize(java.lang.String,byte[]) in javax.management.MBeanServer has been deprecated public ObjectInputStream deserialize(String className, byte[] data) ^ /home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/ connector/rmi/RMIConnectorImpl.java:570: warning: deserialize(javax.management.ObjectName,byte[]) in javax.management.MBeanServer has been deprecated public ObjectInputStream deserialize(ObjectName name, byte[] data) ^ /home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/ connector/ejb/EJBConnector.java:56: warning: deserialize(java.lang.String,javax.management.ObjectName,byte[]) in javax.management.MBeanServer has been deprecated public class EJBConnector ^ /home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/ connector/ejb/EJBConnector.java:56: warning: deserialize(java.lang.String,byte[]) in javax.management.MBeanServer has been deprecated public class EJBConnector ^ /home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/ connector/ejb/EJBConnector.java:56: warning: deserialize(javax.management.ObjectName,byte[]) in javax.management.MBeanServer has been deprecated public class EJBConnector ^ /home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/ connector/ejb/EJBConnector.java:56: warning: deserialize(java.lang.String,javax.management.ObjectName,byte[]) in javax.management.MBeanServer has been deprecated public class EJBConnector ^ /home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/ connector/ejb/EJBConnector.java:56: warning: deserialize(java.lang.String,byte[]) in javax.management.MBeanServer has been deprecated public class EJBConnector ^ /home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/ connector/ejb/EJBConnector.java:56: warning: deserialize(javax.management.ObjectName,byte[]) in javax.management.MBeanServer has been deprecated public class EJBConnector ^ 6 errors 22 warnings BUILD FAILED file:/home/jboss/jbossci/jboss-head/server/build.xml:291: Compile failed; see the compiler error output for details. Total time: 1 minute 55 seconds --- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en _
RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
No, this just allows remote jboss servers to be discovered by browsing the JNDI tree instead of multicast. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Jencks Sent: Saturday, March 08, 2003 7:59 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed Does this change prevent us from writing a remote jndi implementation that runs over the remoting framework? If so, is this the direction we want to go in? david jencks On 2003.03.07 03:10 Tom Elrod wrote: > Build fixed now. Please note that naming is now part of core modules. > This > is due to remoting now requiring naming, since the addition of a JNDI > detector. > > -Tom > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] Behalf Of > > Tom Elrod > > Sent: Friday, March 07, 2003 2:55 AM > > To: [EMAIL PROTECTED] > > Subject: RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > > > > > I did this while in process of doing checkin. Should be fixed in a > > minute. > > > > > -Original Message- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] Behalf Of > > > [EMAIL PROTECTED] > > > Sent: Friday, March 07, 2003 2:34 AM > > > To: [EMAIL PROTECTED] > > > Cc: [EMAIL PROTECTED] > > > Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > > > > > > > > > > > > > > > = > > > ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR > > > DETAILS= > > > > > > > = > > > > > > JAVA VERSION DETAILS > > > java version "1.3.1_06" > > > Java(TM) 2 Runtime Environment, Standard Edition (build > > 1.3.1_06-b01) > > > Java HotSpot(TM) Server VM (build 1.3.1_06-b01, mixed mode) > > > > > > > > > > = > > > > > > HERE ARE THE LAST 50 LINES OF THE LOG FILE > > > > > > [mkdir] Created dir: > > > /home/jboss/jbossci/jboss-head/remoting/output/classes > > > [mkdir] Created dir: > > > /home/jboss/jbossci/jboss-head/remoting/output/gen/classes > > >[depend] Deleted 0 out of date files in 0 seconds > > > [javac] Compiling 62 source files to > > > /home/jboss/jbossci/jboss-head/remoting/output/classes > > > /home/jboss/jbossci/jboss-head/remoting/src/main/org/jboss/rem > > oting/detection/jndi/JNDIDetector.java:19: cannot resolve symbol > > > symbol : class NamingContextFactory > > > location: package interfaces > > > import org.jnp.interfaces.NamingContextFactory; > > > ^ > > > /home/jboss/jbossci/jboss-head/remoting/src/main/org/jboss/rem > > oting/detection/jndi/JNDIDetector.java:20: cannot resolve symbol > > > symbol : class Main > > > location: package server > > > import org.jnp.server.Main; > > > ^ > > > /home/jboss/jbossci/jboss-head/remoting/src/main/test/detectio > > n/jndi/JNDIDetectorTest.java:15: cannot resolve symbol > > > symbol : class Main > > > location: package server > > > import org.jnp.server.Main; > > > ^ > > > /home/jboss/jbossci/jboss-head/remoting/src/main/org/jboss/rem > > oting/detection/jndi/JNDIDetector.java:365: cannot resolve symbol > > > symbol : class Main > > > location: class org.jboss.remoting.detection.jndi.JNDIDetector > > > Main server = new Main(); > > > ^ > > > /home/jboss/jbossci/jboss-head/remoting/src/main/org/jboss/rem > > oting/detection/jndi/JNDIDetector.java:365: cannot resolve symbol > > > symbol : class Main > > > location: class org.jboss.remoting.detection.jndi.JNDIDetector > > > Main server = new Main(); > > > ^ > > > /home/jboss/jbossci/jboss-head/remoting/src/main/org/jboss/rem > > oting/detection/jndi/JNDIDetector.java:370: cannot resolve symbol > > > symbol : class NamingContextFactory > > > location: class org.jboss.remoting.detection.jndi.JNDIDetector > > > contextFactory = > > NamingContextFactory.class.getName(); > > > ^ > > > /home/jboss/jbossci/jboss-head
RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
Does this change prevent us from writing a remote jndi implementation that runs over the remoting framework? If so, is this the direction we want to go in? david jencks On 2003.03.07 03:10 Tom Elrod wrote: > Build fixed now. Please note that naming is now part of core modules. > This > is due to remoting now requiring naming, since the addition of a JNDI > detector. > > -Tom > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] Behalf Of Tom > > Elrod > > Sent: Friday, March 07, 2003 2:55 AM > > To: [EMAIL PROTECTED] > > Subject: RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > > > > > I did this while in process of doing checkin. Should be > > fixed in a minute. > > > > > -Original Message- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] Behalf Of > > > [EMAIL PROTECTED] > > > Sent: Friday, March 07, 2003 2:34 AM > > > To: [EMAIL PROTECTED] > > > Cc: [EMAIL PROTECTED] > > > Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > > > > > > > > > > > > > = > > > ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net > > > FOR DETAILS= > > > > > = > > > > > > JAVA VERSION DETAILS > > > java version "1.3.1_06" > > > Java(TM) 2 Runtime Environment, Standard Edition (build > > 1.3.1_06-b01) > > > Java HotSpot(TM) Server VM (build 1.3.1_06-b01, mixed mode) > > > > > > > > = > > > > > > HERE ARE THE LAST 50 LINES OF THE LOG FILE > > > > > > [mkdir] Created dir: > > > /home/jboss/jbossci/jboss-head/remoting/output/classes > > > [mkdir] Created dir: > > > /home/jboss/jbossci/jboss-head/remoting/output/gen/classes > > >[depend] Deleted 0 out of date files in 0 seconds > > > [javac] Compiling 62 source files to > > > /home/jboss/jbossci/jboss-head/remoting/output/classes > > > /home/jboss/jbossci/jboss-head/remoting/src/main/org/jboss/rem > > oting/detection/jndi/JNDIDetector.java:19: cannot resolve symbol > > > symbol : class NamingContextFactory > > > location: package interfaces > > > import org.jnp.interfaces.NamingContextFactory; > > > ^ > > > /home/jboss/jbossci/jboss-head/remoting/src/main/org/jboss/rem > > oting/detection/jndi/JNDIDetector.java:20: cannot resolve symbol > > > symbol : class Main > > > location: package server > > > import org.jnp.server.Main; > > > ^ > > > /home/jboss/jbossci/jboss-head/remoting/src/main/test/detectio > > n/jndi/JNDIDetectorTest.java:15: cannot resolve symbol > > > symbol : class Main > > > location: package server > > > import org.jnp.server.Main; > > > ^ > > > /home/jboss/jbossci/jboss-head/remoting/src/main/org/jboss/rem > > oting/detection/jndi/JNDIDetector.java:365: cannot resolve symbol > > > symbol : class Main > > > location: class org.jboss.remoting.detection.jndi.JNDIDetector > > > Main server = new Main(); > > > ^ > > > /home/jboss/jbossci/jboss-head/remoting/src/main/org/jboss/rem > > oting/detection/jndi/JNDIDetector.java:365: cannot resolve symbol > > > symbol : class Main > > > location: class org.jboss.remoting.detection.jndi.JNDIDetector > > > Main server = new Main(); > > > ^ > > > /home/jboss/jbossci/jboss-head/remoting/src/main/org/jboss/rem > > oting/detection/jndi/JNDIDetector.java:370: cannot resolve symbol > > > symbol : class NamingContextFactory > > > location: class org.jboss.remoting.detection.jndi.JNDIDetector > > > contextFactory = > > NamingContextFactory.class.getName(); > > > ^ > > > /home/jboss/jbossci/jboss-head/remoting/src/main/test/detectio > > n/jndi/JNDIDetectorTest.java:57: cannot resolve symbol > > > symbol : class Main > > > location: class test.detection.jndi.JNDIDetectorTest > > > Main JNDIServer = new Main(); > > > ^ > > > /home/jboss/jbossci/jboss-head/remoting/src/main/test/detectio > > n/jndi/JNDIDetectorTe
RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
Build fixed now. Please note that naming is now part of core modules. This is due to remoting now requiring naming, since the addition of a JNDI detector. -Tom > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Tom > Elrod > Sent: Friday, March 07, 2003 2:55 AM > To: [EMAIL PROTECTED] > Subject: RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > > I did this while in process of doing checkin. Should be > fixed in a minute. > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] Behalf Of > > [EMAIL PROTECTED] > > Sent: Friday, March 07, 2003 2:34 AM > > To: [EMAIL PROTECTED] > > Cc: [EMAIL PROTECTED] > > Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > > > > > > > > = > > ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net > > FOR DETAILS= > > > = > > > > JAVA VERSION DETAILS > > java version "1.3.1_06" > > Java(TM) 2 Runtime Environment, Standard Edition (build > 1.3.1_06-b01) > > Java HotSpot(TM) Server VM (build 1.3.1_06-b01, mixed mode) > > > > > = > > > > HERE ARE THE LAST 50 LINES OF THE LOG FILE > > > > [mkdir] Created dir: > > /home/jboss/jbossci/jboss-head/remoting/output/classes > > [mkdir] Created dir: > > /home/jboss/jbossci/jboss-head/remoting/output/gen/classes > >[depend] Deleted 0 out of date files in 0 seconds > > [javac] Compiling 62 source files to > > /home/jboss/jbossci/jboss-head/remoting/output/classes > > /home/jboss/jbossci/jboss-head/remoting/src/main/org/jboss/rem > oting/detection/jndi/JNDIDetector.java:19: cannot resolve symbol > > symbol : class NamingContextFactory > > location: package interfaces > > import org.jnp.interfaces.NamingContextFactory; > > ^ > > /home/jboss/jbossci/jboss-head/remoting/src/main/org/jboss/rem > oting/detection/jndi/JNDIDetector.java:20: cannot resolve symbol > > symbol : class Main > > location: package server > > import org.jnp.server.Main; > > ^ > > /home/jboss/jbossci/jboss-head/remoting/src/main/test/detectio > n/jndi/JNDIDetectorTest.java:15: cannot resolve symbol > > symbol : class Main > > location: package server > > import org.jnp.server.Main; > > ^ > > /home/jboss/jbossci/jboss-head/remoting/src/main/org/jboss/rem > oting/detection/jndi/JNDIDetector.java:365: cannot resolve symbol > > symbol : class Main > > location: class org.jboss.remoting.detection.jndi.JNDIDetector > > Main server = new Main(); > > ^ > > /home/jboss/jbossci/jboss-head/remoting/src/main/org/jboss/rem > oting/detection/jndi/JNDIDetector.java:365: cannot resolve symbol > > symbol : class Main > > location: class org.jboss.remoting.detection.jndi.JNDIDetector > > Main server = new Main(); > > ^ > > /home/jboss/jbossci/jboss-head/remoting/src/main/org/jboss/rem > oting/detection/jndi/JNDIDetector.java:370: cannot resolve symbol > > symbol : class NamingContextFactory > > location: class org.jboss.remoting.detection.jndi.JNDIDetector > > contextFactory = > NamingContextFactory.class.getName(); > > ^ > > /home/jboss/jbossci/jboss-head/remoting/src/main/test/detectio > n/jndi/JNDIDetectorTest.java:57: cannot resolve symbol > > symbol : class Main > > location: class test.detection.jndi.JNDIDetectorTest > > Main JNDIServer = new Main(); > > ^ > > /home/jboss/jbossci/jboss-head/remoting/src/main/test/detectio > n/jndi/JNDIDetectorTest.java:57: cannot resolve symbol > > symbol : class Main > > location: class test.detection.jndi.JNDIDetectorTest > > Main JNDIServer = new Main(); > > ^ > > 8 errors > > > > BUILD FAILED > > file:/home/jboss/jbossci/jboss-head/remoting/../tools/etc/buil > dfragments/targets.ent:45: Compile failed; see the compiler > error output for > details. > > Total time: 23 seconds > > > --- > This SF.net email is sponsored by: Etnus, makers of > TotalView, The debugger > for complex code. Debugging C/C++ programs can leave you >
RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
I did this while in process of doing checkin. Should be fixed in a minute. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of > [EMAIL PROTECTED] > Sent: Friday, March 07, 2003 2:34 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > > > = > ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net > FOR DETAILS= > = > > JAVA VERSION DETAILS > java version "1.3.1_06" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_06-b01) > Java HotSpot(TM) Server VM (build 1.3.1_06-b01, mixed mode) > > = > > HERE ARE THE LAST 50 LINES OF THE LOG FILE > > [mkdir] Created dir: > /home/jboss/jbossci/jboss-head/remoting/output/classes > [mkdir] Created dir: > /home/jboss/jbossci/jboss-head/remoting/output/gen/classes >[depend] Deleted 0 out of date files in 0 seconds > [javac] Compiling 62 source files to > /home/jboss/jbossci/jboss-head/remoting/output/classes > /home/jboss/jbossci/jboss-head/remoting/src/main/org/jboss/rem oting/detection/jndi/JNDIDetector.java:19: cannot resolve symbol > symbol : class NamingContextFactory > location: package interfaces > import org.jnp.interfaces.NamingContextFactory; > ^ > /home/jboss/jbossci/jboss-head/remoting/src/main/org/jboss/rem oting/detection/jndi/JNDIDetector.java:20: cannot resolve symbol > symbol : class Main > location: package server > import org.jnp.server.Main; > ^ > /home/jboss/jbossci/jboss-head/remoting/src/main/test/detectio n/jndi/JNDIDetectorTest.java:15: cannot resolve symbol > symbol : class Main > location: package server > import org.jnp.server.Main; > ^ > /home/jboss/jbossci/jboss-head/remoting/src/main/org/jboss/rem oting/detection/jndi/JNDIDetector.java:365: cannot resolve symbol > symbol : class Main > location: class org.jboss.remoting.detection.jndi.JNDIDetector > Main server = new Main(); > ^ > /home/jboss/jbossci/jboss-head/remoting/src/main/org/jboss/rem oting/detection/jndi/JNDIDetector.java:365: cannot resolve symbol > symbol : class Main > location: class org.jboss.remoting.detection.jndi.JNDIDetector > Main server = new Main(); > ^ > /home/jboss/jbossci/jboss-head/remoting/src/main/org/jboss/rem oting/detection/jndi/JNDIDetector.java:370: cannot resolve symbol > symbol : class NamingContextFactory > location: class org.jboss.remoting.detection.jndi.JNDIDetector > contextFactory = NamingContextFactory.class.getName(); > ^ > /home/jboss/jbossci/jboss-head/remoting/src/main/test/detectio n/jndi/JNDIDetectorTest.java:57: cannot resolve symbol > symbol : class Main > location: class test.detection.jndi.JNDIDetectorTest > Main JNDIServer = new Main(); > ^ > /home/jboss/jbossci/jboss-head/remoting/src/main/test/detectio n/jndi/JNDIDetectorTest.java:57: cannot resolve symbol > symbol : class Main > location: class test.detection.jndi.JNDIDetectorTest > Main JNDIServer = new Main(); > ^ > 8 errors > > BUILD FAILED > file:/home/jboss/jbossci/jboss-head/remoting/../tools/etc/buil dfragments/targets.ent:45: Compile failed; see the compiler error output for details. Total time: 23 seconds --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
bandwidth - the more I use, the more it costs me... ;-) Also, I'd like to think that most developers do an update rather than a full checkout and so it helps highlight any issues from that too. ...but I guess the full checkout did not help as it is still failing... Chris --- Jason Dillon <[EMAIL PROTECTED]> wrote: > Why not do a full checkout each day always? > > --jason > > > On Tuesday, March 4, 2003, at 02:56 PM, Chris Kimpton wrote: > > > Hi, > > > > --- David Jencks <[EMAIL PROTECTED]> wrote: > >> I don't think so, the error is not shown. > >> > >> I built fresh from a clean checkout last night with no problems. > >> The > >> problem may be that Chris is not doing a clean checkout every > day. > >> > > > > There is a link on the page to request a full checkout - which I > have > > done - so we can see if that resolves it. > > > > The compile runs on linux - although I do some stuff to ensure a > > specific jdk is used and maybe bypassing any jvm memory changes > that > > have been made - when was this done? > > > > Regards, > > Chris > > > > = > > > > > > __ > > Do you Yahoo!? > > Yahoo! Tax Center - forms, calculators, tips, more > > http://taxes.yahoo.com/ > > > > > > --- > > This SF.net email is sponsored by: Etnus, makers of TotalView, > The > > debugger > > for complex code. Debugging C/C++ programs can leave you feeling > lost > > and > > disoriented. TotalView can help you find your way. Available on > major > > UNIX > > and Linux platforms. Try it free. www.etnus.com > > ___ > > Jboss-development mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > --- > This SF.net email is sponsored by: Etnus, makers of TotalView, The > debugger > for complex code. Debugging C/C++ programs can leave you feeling > lost and > disoriented. TotalView can help you find your way. Available on > major UNIX > and Linux platforms. Try it free. www.etnus.com > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development = __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
Why not do a full checkout each day always? --jason On Tuesday, March 4, 2003, at 02:56 PM, Chris Kimpton wrote: Hi, --- David Jencks <[EMAIL PROTECTED]> wrote: I don't think so, the error is not shown. I built fresh from a clean checkout last night with no problems. The problem may be that Chris is not doing a clean checkout every day. There is a link on the page to request a full checkout - which I have done - so we can see if that resolves it. The compile runs on linux - although I do some stuff to ensure a specific jdk is used and maybe bypassing any jvm memory changes that have been made - when was this done? Regards, Chris = __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
Hi, --- David Jencks <[EMAIL PROTECTED]> wrote: > I don't think so, the error is not shown. > > I built fresh from a clean checkout last night with no problems. > The > problem may be that Chris is not doing a clean checkout every day. > There is a link on the page to request a full checkout - which I have done - so we can see if that resolves it. The compile runs on linux - although I do some stuff to ensure a specific jdk is used and maybe bypassing any jvm memory changes that have been made - when was this done? Regards, Chris = __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
I don't think so, the error is not shown. I built fresh from a clean checkout last night with no problems. The problem may be that Chris is not doing a clean checkout every day. david jencks On 2003.03.03 09:41 Bill Burke wrote: > Is this an XDoclet thing again? > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] Behalf Of > > [EMAIL PROTECTED] > > Sent: Sunday, March 02, 2003 8:41 AM > > To: [EMAIL PROTECTED] > > Cc: [EMAIL PROTECTED] > > Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > > > > > > > = > > ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR > DETAILS= > > = > > > > JAVA VERSION DETAILS > > java version "1.3.1_06" > > Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_06-b01) > > Java HotSpot(TM) Server VM (build 1.3.1_06-b01, mixed mode) > > > > = > > > > HERE ARE THE LAST 50 LINES OF THE LOG FILE > > > > org.jboss.ejb.EJBDeployer --> EJBDeployerMBean qualified to > > EJBDeployerMBean > > org.jboss.ejb.ContainerPlugin --> Service qualified to Service > > org.jboss.ejb.InstanceCache --> StatisticsProvider qualified to > > StatisticsProvider > > org.jboss.ejb.EntityEnterpriseContext --> EJBContextImpl > > qualified to EJBContextImpl > > org.jboss.invocation.Invoker --> Remote qualified to Remote > > org.jboss.ejb.StatefulSessionContainer --> > > AbstractContainerInterceptor qualified to AbstractContainerInterceptor > > org.jboss.ejb.EjbModule --> EjbModuleMBean qualified to EjbModuleMBean > > org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager --> > > StatefulSessionFilePersistenceManagerMBean qualified to > > StatefulSessionFilePersistenceManagerMBean > > org.jboss.ejb.timer.AbstractTimerSource --> > > AbstractTimerSourceMBean qualified to AbstractTimerSourceMBean > > org.jboss.ejb.timer.FilePersistenceManager --> > > FilePersistenceManagerMBean qualified to FilePersistenceManagerMBean > > org.jboss.ejb.timer.SchedulerTimerSource --> > > SchedulerTimerSourceMBean qualified to SchedulerTimerSourceMBean > > org.jboss.invocation.InvokerXAResource --> InvokerXAResourceMBean > > qualified to InvokerXAResourceMBean > > org.jboss.invocation.XATerminatorContainer --> > > XATerminatorContainerMBean qualified to XATerminatorContainerMBean > > org.jboss.invocation.http.server.HttpInvokerMBean --> > > ServiceMBean qualified to ServiceMBean > > org.jboss.invocation.local.LocalInvoker --> LocalInvokerMBean > > qualified to LocalInvokerMBean > > org.jboss.invocation.jrmp.server.JRMPInvoker --> JRMPInvokerMBean > > qualified to JRMPInvokerMBean > > org.jboss.invocation.pooled.server.PooledInvoker --> > > PooledInvokerMBean qualified to PooledInvokerMBean > > org.jboss.invocation.trunk.client.ConnectionManager --> > > ConnectionManagerMBean qualified to ConnectionManagerMBean > > org.jboss.invocation.trunk.client.TrunkInvokerProxy --> > > TrunkInvokerProxyMBean qualified to TrunkInvokerProxyMBean > > org.jboss.invocation.trunk.server.TrunkInvoker --> > > TrunkInvokerMBean qualified to TrunkInvokerMBean > > org.jboss.jms.asf.ServerSessionPoolLoader --> > > ServerSessionPoolLoaderMBean qualified to ServerSessionPoolLoaderMBean > > org.jboss.jms.jndi.JMSProviderLoader --> JMSProviderLoaderMBean > > qualified to JMSProviderLoaderMBean > > org.jboss.jmx.connector.RemoteMBeanServer --> MBeanServer > > qualified to MBeanServer > > org.jboss.jmx.connector.notification.JMSNotificationListener --> > > JMSNotificationListenerMBean qualified to JMSNotificationListenerMBean > > org.jboss.jmx.connector.notification.RMINotificationListener --> > > RMINotificationListenerMBean qualified to RMINotificationListenerMBean > > org.jboss.jmx.adaptor.rmi.RMIAdaptorService --> > > RMIAdaptorServiceMBean qualified to RMIAdaptorServiceMBean > > org.jboss.jmx.adaptor.xml.XMLAdaptorService --> > > XMLAdaptorServiceMBean qualified to XMLAdaptorServiceMBean > > org.jboss.jmx.adaptor.xml.XMLTestService --> XMLTestServiceMBean > > qualified to XMLTestServiceMBean > > org.jboss.jmx.connector.rmi.RMIConnectorImpl --> > > RMIConnectorImplMBean qualified to RMIConnectorImplMBean > > org.jboss.jmx.connector.ejb.EJBConnector --> EJBConnectorMBean > > qualified to EJBConnectorMBean > > org.jboss.jmx.connector.ConnectorFactoryService --> > > ConnectorFactoryServiceMBean qualified to ConnectorFactoryServiceMBean > > org.jboss.jmx.connector.notification.PollingNotificationListener > > --> PollingNotificationListenerMBean qualified to > > PollingNotificationListenerMBean > > org.jboss.logging.Log4jService --> Log4jServiceMBean qualified to > > Log4jServiceMBean > > org.jboss.logging.Log4jSocketServer --> Log4jSocketServerMBean > > qualified to Log4jSocketServerMBean > > org.jboss.naming.ExternalContext --> ExternalContextMBean > > qualified to ExternalConte
RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
Is this an XDoclet thing again? > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of > [EMAIL PROTECTED] > Sent: Sunday, March 02, 2003 8:41 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > > > = > ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS= > = > > JAVA VERSION DETAILS > java version "1.3.1_06" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_06-b01) > Java HotSpot(TM) Server VM (build 1.3.1_06-b01, mixed mode) > > = > > HERE ARE THE LAST 50 LINES OF THE LOG FILE > > org.jboss.ejb.EJBDeployer --> EJBDeployerMBean qualified to > EJBDeployerMBean > org.jboss.ejb.ContainerPlugin --> Service qualified to Service > org.jboss.ejb.InstanceCache --> StatisticsProvider qualified to > StatisticsProvider > org.jboss.ejb.EntityEnterpriseContext --> EJBContextImpl > qualified to EJBContextImpl > org.jboss.invocation.Invoker --> Remote qualified to Remote > org.jboss.ejb.StatefulSessionContainer --> > AbstractContainerInterceptor qualified to AbstractContainerInterceptor > org.jboss.ejb.EjbModule --> EjbModuleMBean qualified to EjbModuleMBean > org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager --> > StatefulSessionFilePersistenceManagerMBean qualified to > StatefulSessionFilePersistenceManagerMBean > org.jboss.ejb.timer.AbstractTimerSource --> > AbstractTimerSourceMBean qualified to AbstractTimerSourceMBean > org.jboss.ejb.timer.FilePersistenceManager --> > FilePersistenceManagerMBean qualified to FilePersistenceManagerMBean > org.jboss.ejb.timer.SchedulerTimerSource --> > SchedulerTimerSourceMBean qualified to SchedulerTimerSourceMBean > org.jboss.invocation.InvokerXAResource --> InvokerXAResourceMBean > qualified to InvokerXAResourceMBean > org.jboss.invocation.XATerminatorContainer --> > XATerminatorContainerMBean qualified to XATerminatorContainerMBean > org.jboss.invocation.http.server.HttpInvokerMBean --> > ServiceMBean qualified to ServiceMBean > org.jboss.invocation.local.LocalInvoker --> LocalInvokerMBean > qualified to LocalInvokerMBean > org.jboss.invocation.jrmp.server.JRMPInvoker --> JRMPInvokerMBean > qualified to JRMPInvokerMBean > org.jboss.invocation.pooled.server.PooledInvoker --> > PooledInvokerMBean qualified to PooledInvokerMBean > org.jboss.invocation.trunk.client.ConnectionManager --> > ConnectionManagerMBean qualified to ConnectionManagerMBean > org.jboss.invocation.trunk.client.TrunkInvokerProxy --> > TrunkInvokerProxyMBean qualified to TrunkInvokerProxyMBean > org.jboss.invocation.trunk.server.TrunkInvoker --> > TrunkInvokerMBean qualified to TrunkInvokerMBean > org.jboss.jms.asf.ServerSessionPoolLoader --> > ServerSessionPoolLoaderMBean qualified to ServerSessionPoolLoaderMBean > org.jboss.jms.jndi.JMSProviderLoader --> JMSProviderLoaderMBean > qualified to JMSProviderLoaderMBean > org.jboss.jmx.connector.RemoteMBeanServer --> MBeanServer > qualified to MBeanServer > org.jboss.jmx.connector.notification.JMSNotificationListener --> > JMSNotificationListenerMBean qualified to JMSNotificationListenerMBean > org.jboss.jmx.connector.notification.RMINotificationListener --> > RMINotificationListenerMBean qualified to RMINotificationListenerMBean > org.jboss.jmx.adaptor.rmi.RMIAdaptorService --> > RMIAdaptorServiceMBean qualified to RMIAdaptorServiceMBean > org.jboss.jmx.adaptor.xml.XMLAdaptorService --> > XMLAdaptorServiceMBean qualified to XMLAdaptorServiceMBean > org.jboss.jmx.adaptor.xml.XMLTestService --> XMLTestServiceMBean > qualified to XMLTestServiceMBean > org.jboss.jmx.connector.rmi.RMIConnectorImpl --> > RMIConnectorImplMBean qualified to RMIConnectorImplMBean > org.jboss.jmx.connector.ejb.EJBConnector --> EJBConnectorMBean > qualified to EJBConnectorMBean > org.jboss.jmx.connector.ConnectorFactoryService --> > ConnectorFactoryServiceMBean qualified to ConnectorFactoryServiceMBean > org.jboss.jmx.connector.notification.PollingNotificationListener > --> PollingNotificationListenerMBean qualified to > PollingNotificationListenerMBean > org.jboss.logging.Log4jService --> Log4jServiceMBean qualified to > Log4jServiceMBean > org.jboss.logging.Log4jSocketServer --> Log4jSocketServerMBean > qualified to Log4jSocketServerMBean > org.jboss.naming.ExternalContext --> ExternalContextMBean > qualified to ExternalContextMBean > org.jboss.naming.JNDIView --> JNDIViewMBean qualified to JNDIViewMBean > org.jboss.naming.NamingAlias --> NamingAliasMBean qualified to > NamingAliasMBean > org.jboss.naming.NamingService --> NamingServiceMBean qualified > to NamingServiceMBean > org.jboss.web.AbstractWebContainer --> AbstractWebContainerMBean > qualified to AbstractWebContainerMBean > WARNING: Some classes refer to other classes that were not f
RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
Oops. I have one more file to check in... - Matt -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 22, 2003 11:38 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed = ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS= = JAVA VERSION DETAILS java version "1.4.1_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01) Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode) = HERE ARE THE LAST 50 LINES OF THE LOG FILE However, since no packages are imported, xjavadoc has assumed that the referred classes belong to the same package as the referring class. The classes are: org.jboss.jdbc.HypersonicDatabase --> HypersonicDatabaseMBean qualified to HypersonicDatabaseMBean org.jboss.jdo.castor.CastorJDOImpl --> CastorJDOImplMBean qualified to CastorJDOImplMBean org.jboss.mail.Email2JMSConverter --> Email2JMSConverterMBean qualified to Email2JMSConverterMBean org.jboss.mail.MailService --> MailServiceMBean qualified to MailServiceMBean org.jboss.services.binding.ServiceBindingManager --> ServiceBindingManagerMBean qualified to ServiceBindingManagerMBean org.jboss.tm.plugins.tyrex.CoordinatorRemoteInterface --> Remote qualified to Remote org.jboss.tm.plugins.tyrex.TransactionManagerService --> TransactionManagerServiceMBean qualified to TransactionManagerServiceMBean org.jboss.varia.autonumber.AutoNumber --> EJBObject qualified to EJBObject org.jboss.varia.autonumber.AutoNumberHome --> EJBHome qualified to EJBHome org.jboss.varia.counter.CounterService --> CounterServiceMBean qualified to CounterServiceMBean org.jboss.varia.deployment.BeanShellSubDeployer --> BeanShellSubDeployerMBean qualified to BeanShellSubDeployerMBean org.jboss.varia.deployment.FoeDeployer --> FoeDeployerMBean qualified to FoeDeployerMBean org.jboss.varia.deployment.convertor.WebLogicConvertor --> WebLogicConvertorMBean qualified to WebLogicConvertorMBean org.jboss.varia.masterconfig.TestService --> TestServiceMBean qualified to TestServiceMBean org.jboss.varia.process.ChildProcessService --> ChildProcessServiceMBean qualified to ChildProcessServiceMBean org.jboss.varia.property.PropertyEditorManagerService --> PropertyEditorManagerServiceMBean qualified to PropertyEditorManagerServiceMBean org.jboss.varia.property.SystemPropertiesService --> SystemPropertiesServiceMBean qualified to SystemPropertiesServiceMBean org.jboss.varia.scheduler.AbstractScheduleProvider --> AbstractScheduleProviderMBean qualified to AbstractScheduleProviderMBean org.jboss.varia.scheduler.DBScheduleProvider --> DBScheduleProviderMBean qualified to DBScheduleProviderMBean org.jboss.varia.scheduler.ScheduleManager --> ScheduleManagerMBean qualified to ScheduleManagerMBean org.jboss.varia.scheduler.Scheduler --> SchedulerMBean qualified to SchedulerMBean org.jboss.varia.scheduler.SingleScheduleProvider --> SingleScheduleProviderMBean qualified to SingleScheduleProviderMBean org.jboss.varia.scheduler.XMLScheduleProvider --> XMLScheduleProviderMBean qualified to XMLScheduleProviderMBean org.jboss.varia.scheduler.example.SchedulableMBeanExample --> SchedulableMBeanExampleMBean qualified to SchedulableMBeanExampleMBean Running Generating output for 'org.jboss.varia.masterconfig.Configurator' using template file 'jar:file:/home/jboss/jbossci/jboss-head/thirdparty/xdoclet-xdoclet/lib/xdoclet-jboss-module-jb4.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. Running Generating output 'transaction-service.xml' using template file 'jar:file:/home/jboss/jbossci/jboss-head/thirdparty/xdoclet-xdoclet/lib/xdoclet-jboss-module-jb4.jar!/xdoclet/modules/jboss/jmx/resources/jboss-service-template.xdt'. INFO:Some classes refer to other classes that were not found among the sources or on the classpath. (Perhaps the referred class doesn't exist? Hasn't been generated yet?) The referring classes do not import any fully qualified classes matching these classes. However, since no packages are imported, xjavadoc has assumed that the referred classes belong to the same package as the referring class. The classes are: org.jboss.varia.masterconfig.TestService --> TestServiceMBean qualified to TestServiceMBean _default:compile-classes: [mkdir] Created dir: /home/jboss/jbossci/jboss-head/varia/output/classes [depend] Deleted 0 out of date files in 0 seconds [javac] Compiling 96 source files to /home/jboss/jbossci/jboss-head/varia/output/classes /home/jboss/jbossci/jboss-head/varia/src/main/org/jboss/varia/masterconfig/Configurator.java:391: getPrimativeClass(java.lang.String) is not public in org.jboss.jmx.adaptor.co
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
No, jboss.net is not compiling, but that is what Dr. Jung was complaining about. The axis libs were updated and a clean build was not done to see what broke. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: "Chris Kimpton" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, January 07, 2003 11:57 AM Subject: Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > Does HEAD compile for anyone else ? > > Chris > > = --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
Does HEAD compile for anyone else ? Chris = __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
oki - i am nobody ! who are u ? ... test failed ! cool ... --- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
I've gotten compiling problems on the 3.0 Branch when using -d. When I stick with just -P life is good. -Fred -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of John Fawcett Sent: Sunday, December 15, 2002 8:55 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed I had this same error on winxp, jdk1.4.1. Manually creating the directory allowed the build to finish. I thought it had something to do with an empty directory in the cache project -- is there supposed to be code in the cache/src/main directory? There are only other empty directories on the cvsview pages at sourceforge. I am using tortoiseCVS to check out. The log says it is using: cvs -q update -d -P CVSROOT=:pserver:[EMAIL PROTECTED]:/cvsroot/jboss I thought the -d flag for update was meant to force empty directory check-outs, so I am still not sure what is going on. Later, fawce -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Scott M Stark Sent: Sunday, December 15, 2002 6:22 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed A clean checkout of jboss-head is compiling for me under JDK1.4.1_01 on win2k and RedHat 8.0 and RedHat 7.3. The issue has to be a conflict with the way the JDK/Ant are running in your environment. Neither environment has ANT_HOME set. What does a build with the -verbose flag passed in show immeadiately before the failure? Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: "Chris Kimpton" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, December 15, 2002 2:06 PM Subject: Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > Hi, > > This crap code is definitely from jboss-head (not jboss-all). > > It compiles fine with jdk1.3 - but fails with jdk1.4. > > Regards, > Chris > > --- [EMAIL PROTECTED] wrote: > > > > > = > > ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR > > DETAILS= > > > = > > > > JAVA VERSION DETAILS > > java version "1.4.1_01" > > Java(TM) 2 Runtime Environment, Standard Edition (build > > 1.4.1_01-b01) > > Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode) > > > > > = > > > > HERE ARE THE LAST 50 LINES OF THE LOG FILE > > > > [mkdir] Created dir: > > /home/jboss/jbossci/jboss-head/aop/output/lib > > [jar] Building jar: > > /home/jboss/jbossci/jboss-head/aop/output/lib/jboss-aop.jar > > > > == > > == > > == Finished 'most' in module 'aop'. > > == > > == > > > > > > _module-aop-most: > > [copy] Copying 1 file to > > /home/jboss/jbossci/jboss-head/build/output/testbuild/lib > > [copy] Copying 1 file to > > /home/jboss/jbossci/jboss-head/build/output/testbuild/lib > > > > == > > == > > == Executing 'most' in module 'cache'... > > == > > == > > > > configure-modules: > > Overriding previous definition of reference to > > jboss.naming.classpath > > > > compile-mbean-sources: > > [mkdir] Created dir: > > /home/jboss/jbossci/jboss-head/cache/output/gen/classes > > /home/jboss/jbossci/jboss-head/cache/src/main not found. > > at > > > org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractF ileSet.java:369) > > at xjavadoc.ant.XJavadocTask.execute(XJavadocTask.java:61) > > at org.apache.tools.ant.Task.perform(Task.java:319) > > at org.apache.tools.ant.Target.execute(Target.java:309) > > at org.apache.tools.ant.Target.performTasks(Target.java:336) > > at org.apache.tools.ant.Project.executeTarget(Project.java:1306) > > at org.jboss.tools.buildmagic.task.Ant.execute(Ant.java:261) > > at > > > org.jboss.tools.buildmagic.task.module.ExecuteModules$1.run(ExecuteModul es.java:329) > > at > > > org.jboss.tools.buildmagic.task.module.ExecuteModules.executeModule(Exec uteModules.java:342) > > at > > > org.jboss.tools.buildmagic.task.module.ExecuteModules.execute(ExecuteMod ules.java:217) > > at > > > org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:166) > > at org.apache.tools.ant.Task.perform(Task.java:319) > >
RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
I had this same error on winxp, jdk1.4.1. Manually creating the directory allowed the build to finish. I thought it had something to do with an empty directory in the cache project -- is there supposed to be code in the cache/src/main directory? There are only other empty directories on the cvsview pages at sourceforge. I am using tortoiseCVS to check out. The log says it is using: cvs -q update -d -P CVSROOT=:pserver:[EMAIL PROTECTED]:/cvsroot/jboss I thought the -d flag for update was meant to force empty directory check-outs, so I am still not sure what is going on. Later, fawce -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Scott M Stark Sent: Sunday, December 15, 2002 6:22 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed A clean checkout of jboss-head is compiling for me under JDK1.4.1_01 on win2k and RedHat 8.0 and RedHat 7.3. The issue has to be a conflict with the way the JDK/Ant are running in your environment. Neither environment has ANT_HOME set. What does a build with the -verbose flag passed in show immeadiately before the failure? Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: "Chris Kimpton" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, December 15, 2002 2:06 PM Subject: Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > Hi, > > This crap code is definitely from jboss-head (not jboss-all). > > It compiles fine with jdk1.3 - but fails with jdk1.4. > > Regards, > Chris > > --- [EMAIL PROTECTED] wrote: > > > > > = > > ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR > > DETAILS= > > > = > > > > JAVA VERSION DETAILS > > java version "1.4.1_01" > > Java(TM) 2 Runtime Environment, Standard Edition (build > > 1.4.1_01-b01) > > Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode) > > > > > = > > > > HERE ARE THE LAST 50 LINES OF THE LOG FILE > > > > [mkdir] Created dir: > > /home/jboss/jbossci/jboss-head/aop/output/lib > > [jar] Building jar: > > /home/jboss/jbossci/jboss-head/aop/output/lib/jboss-aop.jar > > > > == > > == > > == Finished 'most' in module 'aop'. > > == > > == > > > > > > _module-aop-most: > > [copy] Copying 1 file to > > /home/jboss/jbossci/jboss-head/build/output/testbuild/lib > > [copy] Copying 1 file to > > /home/jboss/jbossci/jboss-head/build/output/testbuild/lib > > > > == > > == > > == Executing 'most' in module 'cache'... > > == > > == > > > > configure-modules: > > Overriding previous definition of reference to > > jboss.naming.classpath > > > > compile-mbean-sources: > > [mkdir] Created dir: > > /home/jboss/jbossci/jboss-head/cache/output/gen/classes > > /home/jboss/jbossci/jboss-head/cache/src/main not found. > > at > > > org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractF ileSet.java:369) > > at xjavadoc.ant.XJavadocTask.execute(XJavadocTask.java:61) > > at org.apache.tools.ant.Task.perform(Task.java:319) > > at org.apache.tools.ant.Target.execute(Target.java:309) > > at org.apache.tools.ant.Target.performTasks(Target.java:336) > > at org.apache.tools.ant.Project.executeTarget(Project.java:1306) > > at org.jboss.tools.buildmagic.task.Ant.execute(Ant.java:261) > > at > > > org.jboss.tools.buildmagic.task.module.ExecuteModules$1.run(ExecuteModul es.java:329) > > at > > > org.jboss.tools.buildmagic.task.module.ExecuteModules.executeModule(Exec uteModules.java:342) > > at > > > org.jboss.tools.buildmagic.task.module.ExecuteModules.execute(ExecuteMod ules.java:217) > > at > > > org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:166) > > at org.apache.tools.ant.Task.perform(Task.java:319) > > at org.apache.tools.ant.Target.execute(Target.java:309) > > at org.apache.tools.ant.Target.performTasks(Target.java:336) > > at org.apache.tools.ant.Project.executeTarget(Project.java:1306) > > at org.apache.tools.ant.Project.executeTargets(Project.java:1250) > > at org.apache.tools.ant.Main.runBuild(M
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
Chris, I will dedicate time to do a grep and peplace your .sh /peter PS: and also dub U as the first to get Rewarded ! ; söndagen den 15 december 2002 kl 19.33 skrev [EMAIL PROTECTED]: = ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS= = JAVA VERSION DETAILS java version "1.4.1_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01) Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode) = HERE ARE THE LAST 50 LINES OF THE LOG FILE [mkdir] Created dir: /home/jboss/jbossci/jboss-all/aop/output/lib [jar] Building jar: /home/jboss/jbossci/jboss-all/aop/output/lib/jboss-aop.jar == == == Finished 'most' in module 'aop'. == == _module-aop-most: [copy] Copying 1 file to /home/jboss/jbossci/jboss-all/build/output/testbuild/lib [copy] Copying 1 file to /home/jboss/jbossci/jboss-all/build/output/testbuild/lib == == == Executing 'most' in module 'cache'... == == configure-modules: Overriding previous definition of reference to jboss.naming.classpath compile-mbean-sources: [mkdir] Created dir: /home/jboss/jbossci/jboss-all/cache/output/gen/classes /home/jboss/jbossci/jboss-all/cache/src/main not found. at org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(Abstract FileSet.java:369) at xjavadoc.ant.XJavadocTask.execute(XJavadocTask.java:61) at org.apache.tools.ant.Task.perform(Task.java:319) at org.apache.tools.ant.Target.execute(Target.java:309) at org.apache.tools.ant.Target.performTasks(Target.java:336) at org.apache.tools.ant.Project.executeTarget(Project.java:1306) at org.jboss.tools.buildmagic.task.Ant.execute(Ant.java:261) at org.jboss.tools.buildmagic.task.module.ExecuteModules$1.run(ExecuteModu les.java:329) at org.jboss.tools.buildmagic.task.module.ExecuteModules.executeModule(Exe cuteModules.java:342) at org.jboss.tools.buildmagic.task.module.ExecuteModules.execute(ExecuteMo dules.java:217) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:166) at org.apache.tools.ant.Task.perform(Task.java:319) at org.apache.tools.ant.Target.execute(Target.java:309) at org.apache.tools.ant.Target.performTasks(Target.java:336) at org.apache.tools.ant.Project.executeTarget(Project.java:1306) at org.apache.tools.ant.Project.executeTargets(Project.java:1250) at org.apache.tools.ant.Main.runBuild(Main.java:610) at org.apache.tools.ant.Main.start(Main.java:196) at org.apache.tools.ant.Main.main(Main.java:235) BUILD FAILED file:/home/jboss/jbossci/jboss-all/cache/build.xml:117: Unexpected error Total time: 45 seconds --- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
A clean checkout of jboss-head is compiling for me under JDK1.4.1_01 on win2k and RedHat 8.0 and RedHat 7.3. The issue has to be a conflict with the way the JDK/Ant are running in your environment. Neither environment has ANT_HOME set. What does a build with the -verbose flag passed in show immeadiately before the failure? Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: "Chris Kimpton" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, December 15, 2002 2:06 PM Subject: Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > Hi, > > This crap code is definitely from jboss-head (not jboss-all). > > It compiles fine with jdk1.3 - but fails with jdk1.4. > > Regards, > Chris > > --- [EMAIL PROTECTED] wrote: > > > > > = > > ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR > > DETAILS= > > > = > > > > JAVA VERSION DETAILS > > java version "1.4.1_01" > > Java(TM) 2 Runtime Environment, Standard Edition (build > > 1.4.1_01-b01) > > Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode) > > > > > = > > > > HERE ARE THE LAST 50 LINES OF THE LOG FILE > > > > [mkdir] Created dir: > > /home/jboss/jbossci/jboss-head/aop/output/lib > > [jar] Building jar: > > /home/jboss/jbossci/jboss-head/aop/output/lib/jboss-aop.jar > > > > == > > == > > == Finished 'most' in module 'aop'. > > == > > == > > > > > > _module-aop-most: > > [copy] Copying 1 file to > > /home/jboss/jbossci/jboss-head/build/output/testbuild/lib > > [copy] Copying 1 file to > > /home/jboss/jbossci/jboss-head/build/output/testbuild/lib > > > > == > > == > > == Executing 'most' in module 'cache'... > > == > > == > > > > configure-modules: > > Overriding previous definition of reference to > > jboss.naming.classpath > > > > compile-mbean-sources: > > [mkdir] Created dir: > > /home/jboss/jbossci/jboss-head/cache/output/gen/classes > > /home/jboss/jbossci/jboss-head/cache/src/main not found. > > at > > > >org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractFileSet.java:369) > > at xjavadoc.ant.XJavadocTask.execute(XJavadocTask.java:61) > > at org.apache.tools.ant.Task.perform(Task.java:319) > > at org.apache.tools.ant.Target.execute(Target.java:309) > > at org.apache.tools.ant.Target.performTasks(Target.java:336) > > at org.apache.tools.ant.Project.executeTarget(Project.java:1306) > > at org.jboss.tools.buildmagic.task.Ant.execute(Ant.java:261) > > at > > > org.jboss.tools.buildmagic.task.module.ExecuteModules$1.run(ExecuteModules.java:329) > > at > > > >org.jboss.tools.buildmagic.task.module.ExecuteModules.executeModule(ExecuteModules.java:342) > > at > > > >org.jboss.tools.buildmagic.task.module.ExecuteModules.execute(ExecuteModules.java:217) > > at > > > org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:166) > > at org.apache.tools.ant.Task.perform(Task.java:319) > > at org.apache.tools.ant.Target.execute(Target.java:309) > > at org.apache.tools.ant.Target.performTasks(Target.java:336) > > at org.apache.tools.ant.Project.executeTarget(Project.java:1306) > > at org.apache.tools.ant.Project.executeTargets(Project.java:1250) > > at org.apache.tools.ant.Main.runBuild(Main.java:610) > > at org.apache.tools.ant.Main.start(Main.java:196) > > at org.apache.tools.ant.Main.main(Main.java:235) > > > > BUILD FAILED > > file:/home/jboss/jbossci/jboss-head/cache/build.xml:117: Unexpected > > error > > > > Total time: 48 seconds --- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
Hi, This crap code is definitely from jboss-head (not jboss-all). It compiles fine with jdk1.3 - but fails with jdk1.4. Regards, Chris --- [EMAIL PROTECTED] wrote: > > = > ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR > DETAILS= > = > > JAVA VERSION DETAILS > java version "1.4.1_01" > Java(TM) 2 Runtime Environment, Standard Edition (build > 1.4.1_01-b01) > Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode) > > = > > HERE ARE THE LAST 50 LINES OF THE LOG FILE > > [mkdir] Created dir: > /home/jboss/jbossci/jboss-head/aop/output/lib > [jar] Building jar: > /home/jboss/jbossci/jboss-head/aop/output/lib/jboss-aop.jar > > == > == > == Finished 'most' in module 'aop'. > == > == > > > _module-aop-most: > [copy] Copying 1 file to > /home/jboss/jbossci/jboss-head/build/output/testbuild/lib > [copy] Copying 1 file to > /home/jboss/jbossci/jboss-head/build/output/testbuild/lib > > == > == > == Executing 'most' in module 'cache'... > == > == > > configure-modules: > Overriding previous definition of reference to > jboss.naming.classpath > > compile-mbean-sources: > [mkdir] Created dir: > /home/jboss/jbossci/jboss-head/cache/output/gen/classes > /home/jboss/jbossci/jboss-head/cache/src/main not found. > at > org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractFileSet.java:369) > at xjavadoc.ant.XJavadocTask.execute(XJavadocTask.java:61) > at org.apache.tools.ant.Task.perform(Task.java:319) > at org.apache.tools.ant.Target.execute(Target.java:309) > at org.apache.tools.ant.Target.performTasks(Target.java:336) > at org.apache.tools.ant.Project.executeTarget(Project.java:1306) > at org.jboss.tools.buildmagic.task.Ant.execute(Ant.java:261) > at > org.jboss.tools.buildmagic.task.module.ExecuteModules$1.run(ExecuteModules.java:329) > at > org.jboss.tools.buildmagic.task.module.ExecuteModules.executeModule(ExecuteModules.java:342) > at > org.jboss.tools.buildmagic.task.module.ExecuteModules.execute(ExecuteModules.java:217) > at > org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:166) > at org.apache.tools.ant.Task.perform(Task.java:319) > at org.apache.tools.ant.Target.execute(Target.java:309) > at org.apache.tools.ant.Target.performTasks(Target.java:336) > at org.apache.tools.ant.Project.executeTarget(Project.java:1306) > at org.apache.tools.ant.Project.executeTargets(Project.java:1250) > at org.apache.tools.ant.Main.runBuild(Main.java:610) > at org.apache.tools.ant.Main.start(Main.java:196) > at org.apache.tools.ant.Main.main(Main.java:235) > > BUILD FAILED > file:/home/jboss/jbossci/jboss-head/cache/build.xml:117: Unexpected > error > > Total time: 48 seconds > > > --- > This sf.net email is sponsored by: > With Great Power, Comes Great Responsibility > Learn to use your power at OSDN's High Performance Computing > Channel > http://hpc.devchannel.org/ > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development = __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com --- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
I have requested a clean checkout several times and these are still being generate. It appears the 1.4.1_01 compile is still checking out the old jboss-all alias rather than jboss-head. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Sunday, December 15, 2002 2:34 AM Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > = > ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS= > = > > JAVA VERSION DETAILS > java version "1.4.1_01" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01) > Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode) > > = > > HERE ARE THE LAST 50 LINES OF THE LOG FILE > > [mkdir] Created dir: /home/jboss/jbossci/jboss-all/aop/output/lib > [jar] Building jar: /home/jboss/jbossci/jboss-all/aop/output/lib/jboss-aop.jar > > == > == > == Finished 'most' in module 'aop'. > == > == > > > _module-aop-most: > [copy] Copying 1 file to >/home/jboss/jbossci/jboss-all/build/output/testbuild/lib > [copy] Copying 1 file to >/home/jboss/jbossci/jboss-all/build/output/testbuild/lib > > == > == > == Executing 'most' in module 'cache'... > == > == > > configure-modules: > Overriding previous definition of reference to jboss.naming.classpath > > compile-mbean-sources: > [mkdir] Created dir: /home/jboss/jbossci/jboss-all/cache/output/gen/classes > /home/jboss/jbossci/jboss-all/cache/src/main not found. > at >org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractFileSet.java:369) > at xjavadoc.ant.XJavadocTask.execute(XJavadocTask.java:61) > at org.apache.tools.ant.Task.perform(Task.java:319) > at org.apache.tools.ant.Target.execute(Target.java:309) > at org.apache.tools.ant.Target.performTasks(Target.java:336) > at org.apache.tools.ant.Project.executeTarget(Project.java:1306) > at org.jboss.tools.buildmagic.task.Ant.execute(Ant.java:261) > at >org.jboss.tools.buildmagic.task.module.ExecuteModules$1.run(ExecuteModules.java:329) > at >org.jboss.tools.buildmagic.task.module.ExecuteModules.executeModule(ExecuteModules.java:342) > at >org.jboss.tools.buildmagic.task.module.ExecuteModules.execute(ExecuteModules.java:217) > at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:166) > at org.apache.tools.ant.Task.perform(Task.java:319) > at org.apache.tools.ant.Target.execute(Target.java:309) > at org.apache.tools.ant.Target.performTasks(Target.java:336) > at org.apache.tools.ant.Project.executeTarget(Project.java:1306) > at org.apache.tools.ant.Project.executeTargets(Project.java:1250) > at org.apache.tools.ant.Main.runBuild(Main.java:610) > at org.apache.tools.ant.Main.start(Main.java:196) > at org.apache.tools.ant.Main.main(Main.java:235) > > BUILD FAILED > file:/home/jboss/jbossci/jboss-all/cache/build.xml:117: Unexpected error > > Total time: 46 seconds --- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
Or, from Jason
cd jboss-head/thirdparty
cvs get _thirdparty_apache_slide
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> Adrian Brock
> Sent: Friday, December 13, 2002 5:52 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
>
>
> Full CVS checkout requested.
>
> Regards,
> Adrian
>
> >From: [EMAIL PROTECTED]
> >Reply-To: [EMAIL PROTECTED]
> >To: [EMAIL PROTECTED]
> >CC: [EMAIL PROTECTED]
> >Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
> >Date: Sat, 14 Dec 2002 01:35:29 GMT
> >
> >=
> >==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS=
> >=
> >
> >JAVA VERSION DETAILS
> >java version "1.3.1_06"
> >Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_06-b01)
> >Java HotSpot(TM) Server VM (build 1.3.1_06-b01, mixed mode)
> >
> >=
> >
> >HERE ARE THE LAST 50 LINES OF THE LOG FILE
> >
> >[execmodules]
> >/home/jboss/jbossci/jboss-all/common/src/main/org/jboss/net/proto
col/http/DavURLLister.java:21:
> >cannot resolve symbol
> >[execmodules] symbol : class HttpURL
> >[execmodules] location: package util
> >[execmodules] import org.apache.util.HttpURL;
> >[execmodules]^
> >[execmodules]
> >/home/jboss/jbossci/jboss-all/common/src/main/org/jboss/net/proto
col/http/DavURLLister.java:22:
> >cannot resolve symbol
> >[execmodules] symbol : class WebdavResource
> >[execmodules] location: package lib
> >[execmodules] import org.apache.webdav.lib.WebdavResource;
> >[execmodules] ^
> >[execmodules]
> >/home/jboss/jbossci/jboss-all/common/src/main/org/jboss/logging/X
Priority.java:79:
> >warning: toPriority(java.lang.String) in
> org.apache.log4j.Priority has been
> >deprecated
> >[execmodules]public static Priority toPriority(String name)
> >[execmodules] ^
> >[execmodules]
> >/home/jboss/jbossci/jboss-all/common/src/main/org/jboss/net/proto
col/http/DavURLLister.java:36:
> >cannot resolve symbol
> >[execmodules] symbol : class WebdavResource
> >[execmodules] location: class org.jboss.net.protocol.http.DavURLLister
> >[execmodules] WebdavResource resource = new
> >WebdavResource(baseUrl.toString());
> >[execmodules] ^
> >[execmodules]
> >/home/jboss/jbossci/jboss-all/common/src/main/org/jboss/net/proto
col/http/DavURLLister.java:36:
> >cannot resolve symbol
> >[execmodules] symbol : class WebdavResource
> >[execmodules] location: class org.jboss.net.protocol.http.DavURLLister
> >[execmodules] WebdavResource resource = new
> >WebdavResource(baseUrl.toString());
> >[execmodules]^
> >[execmodules]
> >/home/jboss/jbossci/jboss-all/common/src/main/org/jboss/net/proto
col/http/DavURLLister.java:37:
> >cannot resolve symbol
> >[execmodules] symbol : class WebdavResource
> >[execmodules] location: class org.jboss.net.protocol.http.DavURLLister
> >[execmodules] WebdavResource[] resources =
> >resource.listWebdavResources();
> >[execmodules] ^
> >[execmodules]
> >/home/jboss/jbossci/jboss-all/common/src/main/org/jboss/net/proto
col/http/DavURLLister.java:40:
> >cannot resolve symbol
> >[execmodules] symbol : class WebdavResource
> >[execmodules] location: class org.jboss.net.protocol.http.DavURLLister
> >[execmodules] WebdavResource member = resources[i];
> >[execmodules] ^
> >[execmodules]
> >/home/jboss/jbossci/jboss-all/common/src/main/org/jboss/net/proto
col/http/DavURLLister.java:41:
> >cannot resolve symbol
> >[execmodules] symbol : class HttpURL
> >[execmodules] location: class org.jboss.net.protocol.http.DavURLLister
> >[execmodules] HttpURL httpURL = member.getHttpURL();
> >[execmodules] ^
> >[execmodules]
> >/home/jboss/jbossci/jboss-all/common/src/main/org/jboss/net/proto
col/http/DavURLLister.java:51:
> >cannot resolve symbol
> >[execmodules] symbol : class HttpException
> >[execmodules] location: class org.jboss.net.protocol.http.DavURLLister
> >[execmodules] } catch (HttpException e) {
> >[execmodules]^
> >[execmodules] 9 errors
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
Full CVS checkout requested.
Regards,
Adrian
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
Date: Sat, 14 Dec 2002 01:35:29 GMT
=
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS=
=
JAVA VERSION DETAILS
java version "1.3.1_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_06-b01)
Java HotSpot(TM) Server VM (build 1.3.1_06-b01, mixed mode)
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
[execmodules]
/home/jboss/jbossci/jboss-all/common/src/main/org/jboss/net/protocol/http/DavURLLister.java:21:
cannot resolve symbol
[execmodules] symbol : class HttpURL
[execmodules] location: package util
[execmodules] import org.apache.util.HttpURL;
[execmodules]^
[execmodules]
/home/jboss/jbossci/jboss-all/common/src/main/org/jboss/net/protocol/http/DavURLLister.java:22:
cannot resolve symbol
[execmodules] symbol : class WebdavResource
[execmodules] location: package lib
[execmodules] import org.apache.webdav.lib.WebdavResource;
[execmodules] ^
[execmodules]
/home/jboss/jbossci/jboss-all/common/src/main/org/jboss/logging/XPriority.java:79:
warning: toPriority(java.lang.String) in org.apache.log4j.Priority has been
deprecated
[execmodules]public static Priority toPriority(String name)
[execmodules] ^
[execmodules]
/home/jboss/jbossci/jboss-all/common/src/main/org/jboss/net/protocol/http/DavURLLister.java:36:
cannot resolve symbol
[execmodules] symbol : class WebdavResource
[execmodules] location: class org.jboss.net.protocol.http.DavURLLister
[execmodules] WebdavResource resource = new
WebdavResource(baseUrl.toString());
[execmodules] ^
[execmodules]
/home/jboss/jbossci/jboss-all/common/src/main/org/jboss/net/protocol/http/DavURLLister.java:36:
cannot resolve symbol
[execmodules] symbol : class WebdavResource
[execmodules] location: class org.jboss.net.protocol.http.DavURLLister
[execmodules] WebdavResource resource = new
WebdavResource(baseUrl.toString());
[execmodules]^
[execmodules]
/home/jboss/jbossci/jboss-all/common/src/main/org/jboss/net/protocol/http/DavURLLister.java:37:
cannot resolve symbol
[execmodules] symbol : class WebdavResource
[execmodules] location: class org.jboss.net.protocol.http.DavURLLister
[execmodules] WebdavResource[] resources =
resource.listWebdavResources();
[execmodules] ^
[execmodules]
/home/jboss/jbossci/jboss-all/common/src/main/org/jboss/net/protocol/http/DavURLLister.java:40:
cannot resolve symbol
[execmodules] symbol : class WebdavResource
[execmodules] location: class org.jboss.net.protocol.http.DavURLLister
[execmodules] WebdavResource member = resources[i];
[execmodules] ^
[execmodules]
/home/jboss/jbossci/jboss-all/common/src/main/org/jboss/net/protocol/http/DavURLLister.java:41:
cannot resolve symbol
[execmodules] symbol : class HttpURL
[execmodules] location: class org.jboss.net.protocol.http.DavURLLister
[execmodules] HttpURL httpURL = member.getHttpURL();
[execmodules] ^
[execmodules]
/home/jboss/jbossci/jboss-all/common/src/main/org/jboss/net/protocol/http/DavURLLister.java:51:
cannot resolve symbol
[execmodules] symbol : class HttpException
[execmodules] location: class org.jboss.net.protocol.http.DavURLLister
[execmodules] } catch (HttpException e) {
[execmodules]^
[execmodules] 9 errors
[execmodules] 1 warning
BUILD FAILED
file:/home/jboss/jbossci/jboss-all/common/../tools/etc/buildfragments/targets.ent:45:
Compile failed; see the compiler error output for details.
Total time: 14 seconds
---
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
_
Add photos to your messages with MSN 8. Get 2 months FREE*.
http://join.msn.com/?page=features/featuredemail
---
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
OK guys, we see this message for many hours now.
How about making it compile again ?
These are the little changes I made to get my local copy compile again:
Index: jboss-head/jboss.net/src/main/org/jboss/net/axis/security/SigAuthenticationHandler.java
===
RCS file: /cvsroot/jboss/contrib/jboss.net/src/main/org/jboss/net/axis/security/SigAuthenticationHandler.java,v
retrieving revision 1.2
diff -r1.2 SigAuthenticationHandler.java
134c134
< sgContext.setProperty(MessageContext.AUTHUSER, securityDomain.getActiveSubject());
---
msgContext.setProperty(MessageContext.AUTHUSER, securityDomain.getActiveSubject());
Index: jboss-head/security/src/main/org/jboss/security/plugins/JaasSecurityDomain.java
===
RCS file: /cvsroot/jboss/jbosssx/src/main/org/jboss/security/plugins/JaasSecurityDomain.java,v
retrieving revision 1.6
diff -r1.6 JaasSecurityDomain.java
27a28
import org.jboss.security.auth.callback.SecurityAssociationHandler;
70c71
< super(securityDomain);
---
super(securityDomain, new SecurityAssociationHandler());
Index: jboss-head/security/src/main/org/jboss/security/plugins/JaasSecurityManagerService.java
===
RCS file: /cvsroot/jboss/jbosssx/src/main/org/jboss/security/plugins/JaasSecurityManagerService.java,v
retrieving revision 1.14
diff -r1.14 JaasSecurityManagerService.java
349c349
< CallbackHandler handler = callbackHandlerClass.newInstance();
---
CallbackHandler handler = (CallbackHandler)callbackHandlerClass.newInstance();
Regards
Frank
[EMAIL PROTECTED] wrote:
=
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS=
=
JAVA VERSION DETAILS
java version "1.4.1_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01)
Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode)
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
/home/jboss/jbossci/jboss-all/security/src/main/org/jboss/security/ssl/DomainServerSocketFactory.java:18: warning: com.sun.net.ssl.KeyManagerFactory in com.sun.net.ssl has been deprecated
import com.sun.net.ssl.KeyManagerFactory;
^
/home/jboss/jbossci/jboss-all/security/src/main/org/jboss/security/ssl/DomainServerSocketFactory.java:19: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated
import com.sun.net.ssl.SSLContext;
^
/home/jboss/jbossci/jboss-all/security/src/main/org/jboss/security/ssl/DomainServerSocketFactory.java:20: warning: com.sun.net.ssl.TrustManager in com.sun.net.ssl has been deprecated
import com.sun.net.ssl.TrustManager;
^
/home/jboss/jbossci/jboss-all/security/src/main/org/jboss/security/ssl/DomainServerSocketFactory.java:21: warning: com.sun.net.ssl.TrustManagerFactory in com.sun.net.ssl has been deprecated
import com.sun.net.ssl.TrustManagerFactory;
^
/home/jboss/jbossci/jboss-all/security/src/main/org/jboss/security/ssl/DomainServerSocketFactory.java:43: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated
private transient SSLContext sslCtx = null;
^
/home/jboss/jbossci/jboss-all/security/src/main/org/jboss/security/plugins/JaasSecurityDomain.java:70: cannot resolve symbol
symbol : constructor JaasSecurityManager (java.lang.String)
location: class org.jboss.security.plugins.JaasSecurityManager
super(securityDomain);
^
/home/jboss/jbossci/jboss-all/security/src/main/org/jboss/security/plugins/JaasSecurityDomain.java:216: warning: com.sun.net.ssl.KeyManagerFactory in com.sun.net.ssl has been deprecated
String algorithm = KeyManagerFactory.getDefaultAlgorithm();
^
/home/jboss/jbossci/jboss-all/security/src/main/org/jboss/security/plugins/JaasSecurityDomain.java:217: warning: com.sun.net.ssl.KeyManagerFactory in com.sun.net.ssl has been deprecated
keyMgr = KeyManagerFactory.getInstance(algorithm);
^
/home/jboss/jbossci/jboss-all/security/src/main/org/jboss/security/plugins/JaasSecurityManagerService.java:349: incompatible types
found : java.lang.Object
required: javax.security.auth.callback.CallbackHandler
CallbackHandler handler = callbackHandlerClass.newInstance();
^
/home/jboss/jbossci/jboss-all/security/src/main/org/jboss/security/ssl/DomainServerSocketFactory.java:174: warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated
sslCtx = SSLContext.getInstance("TLS");
^
/home/jboss/jbossci/jboss-all/security/src/main/org/j
RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
Hi, --- marc fleury <[EMAIL PROTECTED]> wrote: > SEE ??? SEE??? > > this is on jboss-all compilation and it doesn't work. Chris missed > the > change to jboss-head it seems No way, jose... its been on jboss-head for a while... - here is my trick - cvs co -d jboss-all jboss-head [I was too lazy to change all my scripts - but now it seems it might be confusing...] Chris > > Guys there is a *SERIOUS** problem with our development > today > and it reads like this: > > Right now everything is lost in the anonymous one-time flow on this > list > (f*cked up) we are going in 1001 directions, which in itself is > good, > but there is no database of changes, read ongoing documentation. > There > is no history of our stuff readily available, documentation on > online > logs of development maintained by individuals. > > THERE IS A CLEAR VISION OF WHERE WE ARE GOING AT LEAST IN THE CORE > GROUP > OF 20 GUYS BUT AS WE GROW BEYOND MOST COMPANIES IN R&D WE NEED TO > COMMUNICATE IT BETTER. > > Killer features are getting lost. > > I will fix it in 2 steps: > > a/ new online/news/blog/wiki development forums WITH ASSIGNED > PEOPLE ON > STAFF that should build a more lasting trace of development > > b/ appoint someone FULL TIME on the documentation, the free one. > Index > it on the sales of the for-pay one. This way the for-pay will pay > for > free one. And we can follow this. > > We will get it right. > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]] On > > Behalf Of [EMAIL PROTECTED] > > Sent: Wednesday, November 27, 2002 6:35 PM > > To: [EMAIL PROTECTED] > > Cc: [EMAIL PROTECTED] > > Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > > > > > > > > = > > ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net > > FOR DETAILS= > > > = > > > > JAVA VERSION DETAILS > > java version "1.3.1_06" > > Java(TM) 2 Runtime Environment, Standard Edition (build > > 1.3.1_06-b01) Java HotSpot(TM) Server VM (build 1.3.1_06-b01, > > mixed mode) > > > > > = > > > > HERE ARE THE LAST 50 LINES OF THE LOG FILE > > > > == Finished 'most' in module 'console'. > > == > == > > > > > > _module-console-most: > > [copy] Copying 5 files to > > /home/jboss/jbossci/jboss-all/build/output/testbuild/bin > > > > == > > == > > == Executing 'most' in module 'security'... > > == > > == > > > > compile-parsers: > > [mkdir] Created dir: > > /home/jboss/jbossci/jboss-all/security/output/parsers/org/jbos > > s/security/auth/login > >[javacc] Java Compiler Compiler Version 2.0 (Parser Generator) > >[javacc] Copyright (c) 1996-2000 Sun Microsystems, Inc. > >[javacc] Copyright (c) 1997-2000 Metamata, Inc. > >[javacc] (type "javacc" with no arguments for help) > >[javacc] Reading from file > > /home/jboss/jbossci/jboss-all/security/src/main/org/jboss/secu > > rity/auth/login/SunConfigParser.jj . . . > >[javacc] File "TokenMgrError.java" does not exist. Will > > create one. > >[javacc] File "ParseException.java" does not exist. Will > > create one. > >[javacc] File "Token.java" does not exist. Will create one. > >[javacc] File "ASCII_CharStream.java" does not exist. > > Will create one. > >[javacc] Parser generated successfully. > > > > compile-classes-jdk13: > > [echo] Compiling for JDK1.3 > > > > do-compile: > > [mkdir] Created dir: > > /home/jboss/jbossci/jboss-all/security/output/classes > > [unjar] Expanding: > > /home/jboss/jbossci/jboss-all/server/output/lib/jboss-security > > .jar into /home/jboss/jbossci/jboss-all/security/output/classes > > [javac] Compiling 136 source files to > > /home/jboss/jbossci/jboss-all/security/output/classes > > /home/jboss/jbossci/jboss-all/security/src/main/org/jboss/secu > > rity/plugins/JaasSecurityDomain.java:70: cannot resolve > > symbol symbol : constructor JaasSecurityManager > (java.lang.String) > > location: class org.jboss.security.plugins.JaasSecurityManager > > super(securityDomain); > > ^ > > /home/jboss/jbossci/jboss-all/security/src/main/org/jboss/secu > > rity/plugins/JaasSecurityManagerService.java:349: incompatible > types > > found : java.lang.Object > > required: javax.security.auth.callback.CallbackHandler > > CallbackHandler handler = > > callbackHandlerClass.newInstance(); > > > > ^ 2 errors > > > > BUILD FAILED > > file:/home/jboss/jbossci/jboss-all/security/build.xml:162: > > Compile failed; see the compiler error output for details. > > > > Total time: 1 minute 37 seconds > > >
RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
SEE ??? SEE??? this is on jboss-all compilation and it doesn't work. Chris missed the change to jboss-head it seems Guys there is a *SERIOUS** problem with our development today and it reads like this: Right now everything is lost in the anonymous one-time flow on this list (f*cked up) we are going in 1001 directions, which in itself is good, but there is no database of changes, read ongoing documentation. There is no history of our stuff readily available, documentation on online logs of development maintained by individuals. THERE IS A CLEAR VISION OF WHERE WE ARE GOING AT LEAST IN THE CORE GROUP OF 20 GUYS BUT AS WE GROW BEYOND MOST COMPANIES IN R&D WE NEED TO COMMUNICATE IT BETTER. Killer features are getting lost. I will fix it in 2 steps: a/ new online/news/blog/wiki development forums WITH ASSIGNED PEOPLE ON STAFF that should build a more lasting trace of development b/ appoint someone FULL TIME on the documentation, the free one. Index it on the sales of the for-pay one. This way the for-pay will pay for free one. And we can follow this. We will get it right. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On > Behalf Of [EMAIL PROTECTED] > Sent: Wednesday, November 27, 2002 6:35 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > > > = > ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net > FOR DETAILS= > = > > JAVA VERSION DETAILS > java version "1.3.1_06" > Java(TM) 2 Runtime Environment, Standard Edition (build > 1.3.1_06-b01) Java HotSpot(TM) Server VM (build 1.3.1_06-b01, > mixed mode) > > = > > HERE ARE THE LAST 50 LINES OF THE LOG FILE > > == Finished 'most' in module 'console'. > == == > > > _module-console-most: > [copy] Copying 5 files to > /home/jboss/jbossci/jboss-all/build/output/testbuild/bin > > == > == > == Executing 'most' in module 'security'... > == > == > > compile-parsers: > [mkdir] Created dir: > /home/jboss/jbossci/jboss-all/security/output/parsers/org/jbos > s/security/auth/login >[javacc] Java Compiler Compiler Version 2.0 (Parser Generator) >[javacc] Copyright (c) 1996-2000 Sun Microsystems, Inc. >[javacc] Copyright (c) 1997-2000 Metamata, Inc. >[javacc] (type "javacc" with no arguments for help) >[javacc] Reading from file > /home/jboss/jbossci/jboss-all/security/src/main/org/jboss/secu > rity/auth/login/SunConfigParser.jj . . . >[javacc] File "TokenMgrError.java" does not exist. Will > create one. >[javacc] File "ParseException.java" does not exist. Will > create one. >[javacc] File "Token.java" does not exist. Will create one. >[javacc] File "ASCII_CharStream.java" does not exist. > Will create one. >[javacc] Parser generated successfully. > > compile-classes-jdk13: > [echo] Compiling for JDK1.3 > > do-compile: > [mkdir] Created dir: > /home/jboss/jbossci/jboss-all/security/output/classes > [unjar] Expanding: > /home/jboss/jbossci/jboss-all/server/output/lib/jboss-security > .jar into /home/jboss/jbossci/jboss-all/security/output/classes > [javac] Compiling 136 source files to > /home/jboss/jbossci/jboss-all/security/output/classes > /home/jboss/jbossci/jboss-all/security/src/main/org/jboss/secu > rity/plugins/JaasSecurityDomain.java:70: cannot resolve > symbol symbol : constructor JaasSecurityManager (java.lang.String) > location: class org.jboss.security.plugins.JaasSecurityManager > super(securityDomain); > ^ > /home/jboss/jbossci/jboss-all/security/src/main/org/jboss/secu > rity/plugins/JaasSecurityManagerService.java:349: incompatible types > found : java.lang.Object > required: javax.security.auth.callback.CallbackHandler > CallbackHandler handler = > callbackHandlerClass.newInstance(); > > ^ 2 errors > > BUILD FAILED > file:/home/jboss/jbossci/jboss-all/security/build.xml:162: > Compile failed; see the compiler error output for details. > > Total time: 1 minute 37 seconds > > > --- > This SF.net email is sponsored by: Get the new Palm Tungsten T > handheld. Power & Color in a compact size! > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en > ___ > Jboss-development mailing list [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > --- This SF.net email is sponsored by: Get the new Palm Tungsten T handh
RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
h it is back and bitching
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On
> Behalf Of [EMAIL PROTECTED]
> Sent: Wednesday, November 27, 2002 3:35 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
>
>
>
> =
> ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net
> FOR DETAILS=
> =
>
> JAVA VERSION DETAILS
> java version "1.4.1_01"
> Java(TM) 2 Runtime Environment, Standard Edition (build
> 1.4.1_01-b01) Java HotSpot(TM) Client VM (build 1.4.1_01-b01,
> mixed mode)
>
> =
>
> HERE ARE THE LAST 50 LINES OF THE LOG FILE
>
>public TrustManagerFactory getTrustManagerFactory() throws
> SecurityException
> ^
> /home/jboss/jbossci/jboss-all/security/src/main/org/jboss/secu
> rity/ssl/DomainServerSocketFactory.java:17: warning:
> com.sun.net.ssl.KeyManager in com.sun.net.ssl has been
> deprecated import com.sun.net.ssl.KeyManager;
>^
> /home/jboss/jbossci/jboss-all/security/src/main/org/jboss/secu
> rity/ssl/DomainServerSocketFactory.java:18: warning:
> com.sun.net.ssl.KeyManagerFactory in com.sun.net.ssl has been
> deprecated import com.sun.net.ssl.KeyManagerFactory;
>^
> /home/jboss/jbossci/jboss-all/security/src/main/org/jboss/secu
> rity/ssl/DomainServerSocketFactory.java:19: warning:
> com.sun.net.ssl.SSLContext in com.sun.net.ssl has been
> deprecated import com.sun.net.ssl.SSLContext;
>^
> /home/jboss/jbossci/jboss-all/security/src/main/org/jboss/secu
> rity/ssl/DomainServerSocketFactory.java:20: warning:
> com.sun.net.ssl.TrustManager in com.sun.net.ssl has been
> deprecated import com.sun.net.ssl.TrustManager;
>^
> /home/jboss/jbossci/jboss-all/security/src/main/org/jboss/secu
> rity/ssl/DomainServerSocketFactory.java:21: warning:
> com.sun.net.ssl.TrustManagerFactory in com.sun.net.ssl has
> been deprecated import com.sun.net.ssl.TrustManagerFactory;
>^
> /home/jboss/jbossci/jboss-all/security/src/main/org/jboss/secu
> rity/ssl/DomainServerSocketFactory.java:43: warning:
> com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated
>private transient SSLContext sslCtx = null;
> ^
> /home/jboss/jbossci/jboss-all/security/src/main/org/jboss/secu
> rity/plugins/JaasSecurityDomain.java:70: cannot resolve
> symbol symbol : constructor JaasSecurityManager (java.lang.String)
> location: class org.jboss.security.plugins.JaasSecurityManager
> super(securityDomain);
> ^
> /home/jboss/jbossci/jboss-all/security/src/main/org/jboss/secu
> rity/plugins/JaasSecurityDomain.java:216: warning:
> com.sun.net.ssl.KeyManagerFactory in com.sun.net.ssl has been
> deprecated
> String algorithm = KeyManagerFactory.getDefaultAlgorithm();
> ^
> /home/jboss/jbossci/jboss-all/security/src/main/org/jboss/secu
> rity/plugins/JaasSecurityDomain.java:217: warning:
> com.sun.net.ssl.KeyManagerFactory in com.sun.net.ssl has been
> deprecated
> keyMgr = KeyManagerFactory.getInstance(algorithm);
> ^
> /home/jboss/jbossci/jboss-all/security/src/main/org/jboss/secu
> rity/ssl/DomainServerSocketFactory.java:174: warning:
> com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated
> sslCtx = SSLContext.getInstance("TLS");
> ^
> /home/jboss/jbossci/jboss-all/security/src/main/org/jboss/secu
> rity/ssl/DomainServerSocketFactory.java:175: warning:
> com.sun.net.ssl.KeyManagerFactory in com.sun.net.ssl has been
> deprecated
> KeyManagerFactory keyMgr =
> securityDomain.getKeyManagerFactory();
> ^
> /home/jboss/jbossci/jboss-all/security/src/main/org/jboss/secu
> rity/ssl/DomainServerSocketFactory.java:178: warning:
> com.sun.net.ssl.TrustManagerFactory in com.sun.net.ssl has
> been deprecated
> TrustManagerFactory trustMgr =
> securityDomain.getTrustManagerFactory();
> ^
> /home/jboss/jbossci/jboss-all/security/src/main/org/jboss/secu
> rity/ssl/DomainServerSocketFactory.java:179: warning:
> com.sun.net.ssl.TrustManager in com.sun.net.ssl has been deprecated
> TrustManager[] trustMgrs = null;
> ^
> 1 error
> 17 warnings
>
> BUILD FAILED
> file:/home/jboss/jbossci/jboss-all/security/build.xml:162:
> Compile failed; see the compiler error output for details.
>
> Total time: 1 minute 35 seconds
>
>
> ---
> This SF.net email is sponsored by: Get the new Palm Tungsten T
> handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
> __
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
Thanks, Adrian fixed it by updating the CVSROOT defs and a clean checkout has been scheduled. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: "Harald Gliebe" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, November 09, 2002 11:43 AM Subject: AW: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed The build failure is caused by jboss.net which uses /thirdparty/apache-commons that is missing in a checkout of jboss-head. After a manual checkout of this module with cvs co -d apache-commons thirdparty/apache/commons in the thirdparty directory, the build succeeds. (verified on linux and win2k). To fix this the jboss-head module needs to include _thirdparty_apache_commons. Regards, harald --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
okey - I did not manage to rename/remove some files yesterday fixing now
fredagen den 8 november 2002 kl 11.19 skrev [EMAIL PROTECTED]:
=
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR
DETAILS=
=
JAVA VERSION DETAILS
java version "1.3.1_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_06-b01)
Java HotSpot(TM) Server VM (build 1.3.1_06-b01, mixed mode)
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
org.jboss.varia.counter.CounterInterceptor --> AbstractInterceptor
qualified to AbstractInterceptor
_default:compile-classes:
[mkdir] Created dir:
/home/jboss/jbossci/jboss-all/varia/output/classes
[depend] Deleted 0 out of date files in 0 seconds
[javac] Compiling 86 source files to
/home/jboss/jbossci/jboss-all/varia/output/classes
/home/jboss/jbossci/jboss-all/varia/src/main/org/hsqldb/1.6.1/
Embedded_ServerConnection.java:89: cannot resolve symbol
symbol : class Channel
location: class org.hsqldb.Embedded_ServerConnection
private Channel init() {
^
/home/jboss/jbossci/jboss-all/varia/src/main/org/hsqldb/1.6.1/
Embedded_DatabaseManager.java:438: work(java.lang.String[]) in
org.hsqldb.util.Transfer cannot be applied to ()
Transfer.work();
^
/home/jboss/jbossci/jboss-all/varia/src/main/org/hsqldb/1.6.1/
Embedded_DatabaseManager.java:440: warning:
setLogStream(java.io.PrintStream) in java.sql.DriverManager has been
deprecated
DriverManager.setLogStream(System.out);
^
/home/jboss/jbossci/jboss-all/varia/src/main/org/hsqldb/1.6.1/
Embedded_DatabaseManager.java:442: warning:
setLogStream(java.io.PrintStream) in java.sql.DriverManager has been
deprecated
DriverManager.setLogStream(null);
^
/home/jboss/jbossci/jboss-all/varia/src/main/org/hsqldb/1.6.1/
Embedded_Server.java:130: cannot resolve symbol
symbol : variable DEFAULT_HSQL_PORT
location: class org.hsqldb.jdbcConnection
port = jdbcConnection.DEFAULT_HSQL_PORT;
^
/home/jboss/jbossci/jboss-all/varia/src/main/org/hsqldb/1.6.1/
Embedded_Server.java:140: warning: setLogStream(java.io.PrintStream)
in java.sql.DriverManager has been deprecated
DriverManager.setLogStream(System.out);
^
/home/jboss/jbossci/jboss-all/varia/src/main/org/hsqldb/1.6.1/
Embedded_ServerConnection.java:100: cannot resolve symbol
symbol : class Channel
location: class org.hsqldb.Embedded_ServerConnection
Channel c;
^
/home/jboss/jbossci/jboss-all/varia/src/main/org/hsqldb/1.6.1/
Embedded_ServerConnection.java:107: cannot resolve symbol
symbol : constructor Result (java.lang.String)
location: class org.hsqldb.Result
write(new Result(e.getMessage()).getBytes());
^
/home/jboss/jbossci/jboss-all/varia/src/main/org/hsqldb/1.6.1/
Embedded_ServerConnection.java:119: cannot resolve symbol
symbol : class Channel
location: class org.hsqldb.Embedded_ServerConnection
Channel c = init();
^
6 errors
3 warnings
BUILD FAILED
file:/home/jboss/jbossci/jboss-all/varia/../tools/etc/buildfragments/
targets.ent:45: Compile failed; see the compiler error output for
details.
Total time: 2 minutes 18 seconds
---
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
---
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
hehe ... just pushed the button for a clean checkout at lubega and it
even answers. Hopefully this will take care of it !
***
The next jboss rebuild will do a full cvs checkout - cool!
TIME NOW: Fri Nov 8 08:57:55 GMT 2002
fredagen den 8 november 2002 kl 09.19 skrev [EMAIL PROTECTED]:
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
JAVA VERSION DETAILS
java version "1.3.1_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_06-b01)
Java HotSpot(TM) Server VM (build 1.3.1_06-b01, mixed mode)
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
org.jboss.varia.counter.CounterInterceptor --> AbstractInterceptor
qualified to AbstractInterceptor
_default:compile-classes:
[mkdir] Created dir:
/disk/orig/home/lubega/jbossro/jboss-all/varia/output/classes
[depend] Deleted 0 out of date files in 0 seconds
[javac] Compiling 86 source files to
/disk/orig/home/lubega/jbossro/jboss-all/varia/output/classes
/disk/orig/home/lubega/jbossro/jboss-all/varia/src/main/org/hsqldb/
1.6.1/Embedded_ServerConnection.java:89: cannot resolve symbol
symbol : class Channel
location: class org.hsqldb.Embedded_ServerConnection
private Channel init() {
^
/disk/orig/home/lubega/jbossro/jboss-all/varia/src/main/org/hsqldb/
1.6.1/Embedded_DatabaseManager.java:438: work(java.lang.String[]) in
org.hsqldb.util.Transfer cannot be applied to ()
Transfer.work();
^
/disk/orig/home/lubega/jbossro/jboss-all/varia/src/main/org/hsqldb/
1.6.1/Embedded_DatabaseManager.java:440: warning:
setLogStream(java.io.PrintStream) in java.sql.DriverManager has been
deprecated
DriverManager.setLogStream(System.out);
^
/disk/orig/home/lubega/jbossro/jboss-all/varia/src/main/org/hsqldb/
1.6.1/Embedded_DatabaseManager.java:442: warning:
setLogStream(java.io.PrintStream) in java.sql.DriverManager has been
deprecated
DriverManager.setLogStream(null);
^
/disk/orig/home/lubega/jbossro/jboss-all/varia/src/main/org/hsqldb/
1.6.1/Embedded_Server.java:130: cannot resolve symbol
symbol : variable DEFAULT_HSQL_PORT
location: class org.hsqldb.jdbcConnection
port = jdbcConnection.DEFAULT_HSQL_PORT;
^
/disk/orig/home/lubega/jbossro/jboss-all/varia/src/main/org/hsqldb/
1.6.1/Embedded_Server.java:140: warning:
setLogStream(java.io.PrintStream) in java.sql.DriverManager has been
deprecated
DriverManager.setLogStream(System.out);
^
/disk/orig/home/lubega/jbossro/jboss-all/varia/src/main/org/hsqldb/
1.6.1/Embedded_ServerConnection.java:100: cannot resolve symbol
symbol : class Channel
location: class org.hsqldb.Embedded_ServerConnection
Channel c;
^
/disk/orig/home/lubega/jbossro/jboss-all/varia/src/main/org/hsqldb/
1.6.1/Embedded_ServerConnection.java:107: cannot resolve symbol
symbol : constructor Result (java.lang.String)
location: class org.hsqldb.Result
write(new Result(e.getMessage()).getBytes());
^
/disk/orig/home/lubega/jbossro/jboss-all/varia/src/main/org/hsqldb/
1.6.1/Embedded_ServerConnection.java:119: cannot resolve symbol
symbol : class Channel
location: class org.hsqldb.Embedded_ServerConnection
Channel c = init();
^
6 errors
3 warnings
BUILD FAILED
file:/disk/orig/home/lubega/jbossro/jboss-all/varia/../tools/etc/
buildfragments/targets.ent:45: Compile failed; see the compiler error
output for details.
Total time: 4 minutes 41 seconds
---
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
---
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
I think this is a JDK 1.4 thing... I'll re-write it JDK 1.3.x compilant... - Matt -Original Message- From: [EMAIL PROTECTED] [mailto:jboss-development-admin@;lists.sourceforge.net]On Behalf Of [EMAIL PROTECTED] Sent: Friday, October 18, 2002 1:35 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed = ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= = JAVA VERSION DETAILS java version "1.3.1_03" Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03) Java HotSpot(TM) Server VM (build 1.3.1_03-b03, mixed mode) = HERE ARE THE LAST 50 LINES OF THE LOG FILE [mkdir] Created dir: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/gen/classes _default:compile-classes: [mkdir] Created dir: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/classes [depend] Deleted 0 out of date files in 0 seconds [javac] Compiling 557 source files to /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/classes /disk/orig/home/lubega/jbossro/jboss-all/jmx/src/main/org/jboss/mx/logging/l og4j/Log4jAdapter.java:58: warning: getPriority() in org.apache.log4j.Category has been deprecated return category.getPriority().toInt(); ^ /disk/orig/home/lubega/jbossro/jboss-all/jmx/src/main/org/jboss/mx/logging/l og4j/Log4jAdapter.java:64: warning: setPriority(org.apache.log4j.Priority) in org.apache.log4j.Category has been deprecated category.setPriority(Priority.toPriority(level)); ^ /disk/orig/home/lubega/jbossro/jboss-all/jmx/src/main/org/jboss/mx/logging/l og4j/Log4jAdapter.java:82: warning: getChainedPriority() in org.apache.log4j.Category has been deprecated return p.isGreaterOrEqual(category.getChainedPriority()); ^ /disk/orig/home/lubega/jbossro/jboss-all/jmx/src/main/org/jboss/mx/logging/l og4j/Log4jAdapter.java:100: warning: getChainedPriority() in org.apache.log4j.Category has been deprecated return p.isGreaterOrEqual(category.getChainedPriority()); ^ /disk/orig/home/lubega/jbossro/jboss-all/jmx/src/main/org/jboss/mx/logging/l og4j/Log4jAdapter.java:118: warning: getChainedPriority() in org.apache.log4j.Category has been deprecated return p.isGreaterOrEqual(category.getChainedPriority()); ^ /disk/orig/home/lubega/jbossro/jboss-all/jmx/src/main/org/jboss/mx/logging/l og4j/Log4jAdapter.java:136: warning: getChainedPriority() in org.apache.log4j.Category has been deprecated return p.isGreaterOrEqual(category.getChainedPriority()); ^ /disk/orig/home/lubega/jbossro/jboss-all/jmx/src/main/org/jboss/mx/logging/l og4j/Log4jAdapter.java:154: warning: getChainedPriority() in org.apache.log4j.Category has been deprecated return p.isGreaterOrEqual(category.getChainedPriority()); ^ /disk/orig/home/lubega/jbossro/jboss-all/jmx/src/main/org/jboss/mx/logging/l og4j/Log4jAdapter.java:172: warning: getChainedPriority() in org.apache.log4j.Category has been deprecated return p.isGreaterOrEqual(category.getChainedPriority()); ^ /disk/orig/home/lubega/jbossro/jboss-all/jmx/src/main/org/jboss/mx/logging/l og4j/Log4jAdapter.java:190: warning: getChainedPriority() in org.apache.log4j.Category has been deprecated return p.isGreaterOrEqual(category.getChainedPriority()); ^ /disk/orig/home/lubega/jbossro/jboss-all/jmx/src/main/org/jboss/mx/persisten ce/MbeanInfoDbPm.java:279: cannot resolve symbol symbol : method replaceAll (java.lang.String,java.lang.String) location: class java.lang.String fileName = fileName.replaceAll(objNameSeparator(), objNameSepRep()); ^ /disk/orig/home/lubega/jbossro/jboss-all/jmx/src/main/org/jboss/mx/persisten ce/MbeanInfoDbPm.java:288: cannot resolve symbol symbol : method replaceAll (java.lang.String,java.lang.String) location: class java.lang.String objectName = objectName.replaceAll(objNameSepRep(), objNameSeparator()); ^ 2 errors 9 warnings BUILD FAILED file:/disk/orig/home/lubega/jbossro/jboss-all/jmx/../tools/etc/buildfragment s/targets.ent:45: Compile failed; see the compiler error output for details. Total time: 49 seconds --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This sf.net emai
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
CVS update will work, but you will need to follow the instructions to update your thirdparty directory for HEAD. --jason On 9 Oct 2002, Christian Riege wrote: > On Tue, 2002-10-08 at 20:55, Scott M Stark wrote: > > [...] > > The head revision cannot be checked out using the jboss-all module alias any >longer. > > does this imply that I _must_ do a full clean checkout of my local CVS > copies of all 3 branches using the commands you posted to get a correct > working copy? or can i stick w/ 'cvs upd' for the meantime? > > regards, > christian > > > > --- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
On Tue, 2002-10-08 at 20:55, Scott M Stark wrote: > [...] > The head revision cannot be checked out using the jboss-all module alias any longer. does this imply that I _must_ do a full clean checkout of my local CVS copies of all 3 branches using the commands you posted to get a correct working copy? or can i stick w/ 'cvs upd' for the meantime? regards, christian --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
The head revision cannot be checked out using the jboss-all module alias any longer. The jboss-head alias must be used instead. If you successfully wade through the dump of CVSROOT/module changes and associated mails this is the summary statement: - To checkout 3.0 use: cvs co -r Branch_3_0 jboss-all-> a jboss-all directory with the current 3.0 structure or cvs co -r Branch_3_0 jboss-3.0-> a jboss-3.0 directory with the current 3.0 structure - To checkout 3.2 use: cvs co -r Branch_3_2 jboss-3.2-> a jboss-3.2 directory with the current 3.2 structure - To checkout main/4.0 alpha cvs co jboss-head-> a jboss-head directory with the current main branch So, jboss-all is bound to the 3.0 release for now until the end of time. All future branches will have a module alias that reflects the version number to avoid the problems of CVS not versioning its metadata. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: "Chris Kimpton" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 08, 2002 4:30 AM Subject: Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > Hi, > > > > > _buildmagic:init: > > Trying to override old definition of task property > > > > BUILD FAILED > > > >file:/disk/orig/home/lubega/jbossro/jboss-all/build/../tools/etc/buildfragments/tools.ent:29: > > taskdef class xdoclet.modules.jmx.JMXDocletTask cannot be found > > > > We've got past the other problems - but still have this one - is it > just me - or is there really a problem here? > > I did a full checkout earlier - so it should be up to date. > > Chris --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
I had the same problem yesterday. I've deleted jboss-all (and directory jboss which temporary existed) and made a new checkout. Now compilation is fine again. Regards Frank Chris Kimpton wrote: >Hi, > > > >>_buildmagic:init: >>Trying to override old definition of task property >> >>BUILD FAILED >> >> >> >file:/disk/orig/home/lubega/jbossro/jboss-all/build/../tools/etc/buildfragments/tools.ent:29: > > >>taskdef class xdoclet.modules.jmx.JMXDocletTask cannot be found >> >> >> > >We've got past the other problems - but still have this one - is it >just me - or is there really a problem here? > >I did a full checkout earlier - so it should be up to date. > >Chris > >= > > >__ >Do you Yahoo!? >Faith Hill - Exclusive Performances, Videos & More >http://faith.yahoo.com > > >--- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >___ >Jboss-development mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/jboss-development > > > --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
Hi, > > _buildmagic:init: > Trying to override old definition of task property > > BUILD FAILED > file:/disk/orig/home/lubega/jbossro/jboss-all/build/../tools/etc/buildfragments/tools.ent:29: > taskdef class xdoclet.modules.jmx.JMXDocletTask cannot be found > We've got past the other problems - but still have this one - is it just me - or is there really a problem here? I did a full checkout earlier - so it should be up to date. Chris = __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
Does anyone know where the scripts for these tests are kept? --jason On Mon, 7 Oct 2002, marc fleury wrote: > But seriously now, can anyone get Chris on the line, he needs to clean > the disk and checkout... this is embarassing > > marc f > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]] On > > Behalf Of Lennart Petersson > > Sent: Monday, October 07, 2002 9:15 AM > > To: [EMAIL PROTECTED] > > Subject: Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > > > > > It's the ultimate solution of the build mess - simplify you know :) > > > > /Lennart > > > > måndagen den 7 oktober 2002 kl 14.55 skrev Sacha Labourey: > > > > > It is a new undocummented feature. Cool, huh? > > > > > >> -Message d'origine- > > >> De : [EMAIL PROTECTED] > > >> [mailto:[EMAIL PROTECTED]]De la part de > > >> marc > > >> fleury > > >> Envoye : lundi, 7 octobre 2002 14:51 > > >> A : [EMAIL PROTECTED] > > >> Objet : RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > >> > > >> > > >> WTF? > > >> > > >> marc f > > >> > > >>> -Original Message- > > >>> From: [EMAIL PROTECTED] > > >>> [mailto:[EMAIL PROTECTED]] On > > Behalf Of > > >>> [EMAIL PROTECTED] > > >>> Sent: Monday, October 07, 2002 8:15 AM > > >>> To: [EMAIL PROTECTED] > > >>> Cc: [EMAIL PROTECTED] > > >>> Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > >>> > > >>> > > >>> > > >>> > > > > >>> = > > >>> ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR > > >>> DETAILS= > > >>> > > = > > >>> > > >>> JAVA VERSION DETAILS > > >>> java version "1.4.0_01" > > >>> Java(TM) 2 Runtime Environment, Standard Edition (build > > >>> 1.4.0_01-b03) Java HotSpot(TM) Client VM (build > > 1.4.0_01-b03, mixed > > >>> mode) > > >>> > > >>> > > > > >>> = > > >>> > > >>> HERE ARE THE LAST 50 LINES OF THE LOG FILE > > >>> > > >>> build.sh: build.sh: No such file or directory > > >>> > > >>> > > >>> --- > > >>> This sf.net email is sponsored by:ThinkGeek > > >>> Welcome to geek heaven. > > >>> http://thinkgeek.com/sf > > >>> ___ > > >>> Jboss-development mailing list > > >>> [EMAIL PROTECTED] > > >>> https://lists.sourceforge.net/lists/listinfo/jboss-development > > >>> > > >> > > >> > > >> > > >> --- > > >> This sf.net email is sponsored by:ThinkGeek > > >> Welcome to geek heaven. > > >> http://thinkgeek.com/sf > > >> ___ > > >> Jboss-development mailing list > > >> [EMAIL PROTECTED] > > >> https://lists.sourceforge.net/lists/listinfo/jboss-development > > >> > > > > > > > > > --- > > > This sf.net email is sponsored by:ThinkGeek > > > Welcome to geek heaven. > > > http://thinkgeek.com/sf > > > ___ > > > Jboss-development mailing list > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > > > --- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > ___ > > Jboss-development mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > --- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
The nightly build is not very inteligent... --jason On Mon, 7 Oct 2002, Sacha Labourey wrote: > It is a new undocummented feature. Cool, huh? > > > -Message d'origine- > > De : [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]De la part de marc > > fleury > > Envoye : lundi, 7 octobre 2002 14:51 > > A : [EMAIL PROTECTED] > > Objet : RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > > > > > WTF? > > > > marc f > > > > > -Original Message- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED]] On > > > Behalf Of [EMAIL PROTECTED] > > > Sent: Monday, October 07, 2002 8:15 AM > > > To: [EMAIL PROTECTED] > > > Cc: [EMAIL PROTECTED] > > > Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > > > > > > > > > > > = > > > ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR > > > DETAILS= > > > = > > > > > > JAVA VERSION DETAILS > > > java version "1.4.0_01" > > > Java(TM) 2 Runtime Environment, Standard Edition (build > > > 1.4.0_01-b03) Java HotSpot(TM) Client VM (build 1.4.0_01-b03, > > > mixed mode) > > > > > > = > > > > > > HERE ARE THE LAST 50 LINES OF THE LOG FILE > > > > > > build.sh: build.sh: No such file or directory > > > > > > > > > --- > > > This sf.net email is sponsored by:ThinkGeek > > > Welcome to geek heaven. > > > http://thinkgeek.com/sf > > > ___ > > > Jboss-development mailing list [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > > > > > > --- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > ___ > > Jboss-development mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > --- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
But seriously now, can anyone get Chris on the line, he needs to clean the disk and checkout... this is embarassing marc f > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On > Behalf Of Lennart Petersson > Sent: Monday, October 07, 2002 9:15 AM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > > It's the ultimate solution of the build mess - simplify you know :) > > /Lennart > > måndagen den 7 oktober 2002 kl 14.55 skrev Sacha Labourey: > > > It is a new undocummented feature. Cool, huh? > > > >> -Message d'origine- > >> De : [EMAIL PROTECTED] > >> [mailto:[EMAIL PROTECTED]]De la part de > >> marc > >> fleury > >> Envoye : lundi, 7 octobre 2002 14:51 > >> A : [EMAIL PROTECTED] > >> Objet : RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > >> > >> > >> WTF? > >> > >> marc f > >> > >>> -Original Message- > >>> From: [EMAIL PROTECTED] > >>> [mailto:[EMAIL PROTECTED]] On > Behalf Of > >>> [EMAIL PROTECTED] > >>> Sent: Monday, October 07, 2002 8:15 AM > >>> To: [EMAIL PROTECTED] > >>> Cc: [EMAIL PROTECTED] > >>> Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > >>> > >>> > >>> > >>> > > >>> = > >>> ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR > >>> DETAILS= > >>> > = > >>> > >>> JAVA VERSION DETAILS > >>> java version "1.4.0_01" > >>> Java(TM) 2 Runtime Environment, Standard Edition (build > >>> 1.4.0_01-b03) Java HotSpot(TM) Client VM (build > 1.4.0_01-b03, mixed > >>> mode) > >>> > >>> > > >>> = > >>> > >>> HERE ARE THE LAST 50 LINES OF THE LOG FILE > >>> > >>> build.sh: build.sh: No such file or directory > >>> > >>> > >>> --- > >>> This sf.net email is sponsored by:ThinkGeek > >>> Welcome to geek heaven. > >>> http://thinkgeek.com/sf > >>> ___ > >>> Jboss-development mailing list > >>> [EMAIL PROTECTED] > >>> https://lists.sourceforge.net/lists/listinfo/jboss-development > >>> > >> > >> > >> > >> --- > >> This sf.net email is sponsored by:ThinkGeek > >> Welcome to geek heaven. > >> http://thinkgeek.com/sf > >> ___ > >> Jboss-development mailing list > >> [EMAIL PROTECTED] > >> https://lists.sourceforge.net/lists/listinfo/jboss-development > >> > > > > > > --- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > ___ > > Jboss-development mailing list > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > --- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
he he he, actual LOL we don't have a build problem anymore, that fucking piece of radioactive dunk just went boom... marc f > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On > Behalf Of Lennart Petersson > Sent: Monday, October 07, 2002 9:15 AM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > > It's the ultimate solution of the build mess - simplify you know :) > > /Lennart > > måndagen den 7 oktober 2002 kl 14.55 skrev Sacha Labourey: > > > It is a new undocummented feature. Cool, huh? > > > >> -Message d'origine- > >> De : [EMAIL PROTECTED] > >> [mailto:[EMAIL PROTECTED]]De la part de > >> marc > >> fleury > >> Envoye : lundi, 7 octobre 2002 14:51 > >> A : [EMAIL PROTECTED] > >> Objet : RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > >> > >> > >> WTF? > >> > >> marc f > >> > >>> -Original Message- > >>> From: [EMAIL PROTECTED] > >>> [mailto:[EMAIL PROTECTED]] On > Behalf Of > >>> [EMAIL PROTECTED] > >>> Sent: Monday, October 07, 2002 8:15 AM > >>> To: [EMAIL PROTECTED] > >>> Cc: [EMAIL PROTECTED] > >>> Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > >>> > >>> > >>> > >>> > > >>> = > >>> ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR > >>> DETAILS= > >>> > = > >>> > >>> JAVA VERSION DETAILS > >>> java version "1.4.0_01" > >>> Java(TM) 2 Runtime Environment, Standard Edition (build > >>> 1.4.0_01-b03) Java HotSpot(TM) Client VM (build > 1.4.0_01-b03, mixed > >>> mode) > >>> > >>> > > >>> = > >>> > >>> HERE ARE THE LAST 50 LINES OF THE LOG FILE > >>> > >>> build.sh: build.sh: No such file or directory > >>> > >>> > >>> --- > >>> This sf.net email is sponsored by:ThinkGeek > >>> Welcome to geek heaven. > >>> http://thinkgeek.com/sf > >>> ___ > >>> Jboss-development mailing list > >>> [EMAIL PROTECTED] > >>> https://lists.sourceforge.net/lists/listinfo/jboss-development > >>> > >> > >> > >> > >> --- > >> This sf.net email is sponsored by:ThinkGeek > >> Welcome to geek heaven. > >> http://thinkgeek.com/sf > >> ___ > >> Jboss-development mailing list > >> [EMAIL PROTECTED] > >> https://lists.sourceforge.net/lists/listinfo/jboss-development > >> > > > > > > --- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > ___ > > Jboss-development mailing list > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > --- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
>>> = >>> >>> HERE ARE THE LAST 50 LINES OF THE LOG FILE >>> >>> build.sh: build.sh: No such file or directory When doing a clean co jboss-all the folder dloaded comes as jboss and not as jboss-all as expected. This probably freaks out some script at lubega ? /peter_f --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
It's the ultimate solution of the build mess - simplify you know :) /Lennart måndagen den 7 oktober 2002 kl 14.55 skrev Sacha Labourey: > It is a new undocummented feature. Cool, huh? > >> -Message d'origine- >> De : [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED]]De la part de >> marc >> fleury >> Envoye : lundi, 7 octobre 2002 14:51 >> A : [EMAIL PROTECTED] >> Objet : RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed >> >> >> WTF? >> >> marc f >> >>> -Original Message- >>> From: [EMAIL PROTECTED] >>> [mailto:[EMAIL PROTECTED]] On >>> Behalf Of [EMAIL PROTECTED] >>> Sent: Monday, October 07, 2002 8:15 AM >>> To: [EMAIL PROTECTED] >>> Cc: [EMAIL PROTECTED] >>> Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed >>> >>> >>> >>> = >>> ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR >>> DETAILS= >>> = >>> >>> JAVA VERSION DETAILS >>> java version "1.4.0_01" >>> Java(TM) 2 Runtime Environment, Standard Edition (build >>> 1.4.0_01-b03) Java HotSpot(TM) Client VM (build 1.4.0_01-b03, >>> mixed mode) >>> >>> = >>> >>> HERE ARE THE LAST 50 LINES OF THE LOG FILE >>> >>> build.sh: build.sh: No such file or directory >>> >>> >>> --- >>> This sf.net email is sponsored by:ThinkGeek >>> Welcome to geek heaven. >>> http://thinkgeek.com/sf >>> ___ >>> Jboss-development mailing list >>> [EMAIL PROTECTED] >>> https://lists.sourceforge.net/lists/listinfo/jboss-development >>> >> >> >> >> --- >> This sf.net email is sponsored by:ThinkGeek >> Welcome to geek heaven. >> http://thinkgeek.com/sf >> ___ >> Jboss-development mailing list >> [EMAIL PROTECTED] >> https://lists.sourceforge.net/lists/listinfo/jboss-development >> > > > --- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
It is a new undocummented feature. Cool, huh? > -Message d'origine- > De : [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]De la part de marc > fleury > Envoye : lundi, 7 octobre 2002 14:51 > A : [EMAIL PROTECTED] > Objet : RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > > WTF? > > marc f > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]] On > > Behalf Of [EMAIL PROTECTED] > > Sent: Monday, October 07, 2002 8:15 AM > > To: [EMAIL PROTECTED] > > Cc: [EMAIL PROTECTED] > > Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > > > > > > > = > > ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR > > DETAILS= > > = > > > > JAVA VERSION DETAILS > > java version "1.4.0_01" > > Java(TM) 2 Runtime Environment, Standard Edition (build > > 1.4.0_01-b03) Java HotSpot(TM) Client VM (build 1.4.0_01-b03, > > mixed mode) > > > > = > > > > HERE ARE THE LAST 50 LINES OF THE LOG FILE > > > > build.sh: build.sh: No such file or directory > > > > > > --- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > ___ > > Jboss-development mailing list [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > --- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
WTF? marc f > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On > Behalf Of [EMAIL PROTECTED] > Sent: Monday, October 07, 2002 8:15 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > > > = > ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR > DETAILS= > = > > JAVA VERSION DETAILS > java version "1.4.0_01" > Java(TM) 2 Runtime Environment, Standard Edition (build > 1.4.0_01-b03) Java HotSpot(TM) Client VM (build 1.4.0_01-b03, > mixed mode) > > = > > HERE ARE THE LAST 50 LINES OF THE LOG FILE > > build.sh: build.sh: No such file or directory > > > --- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > ___ > Jboss-development mailing list [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
I believe this might be resolved by forcing a full checkout... but I can't get to lubega.com at the moment... --jason > -Original Message- > From: [EMAIL PROTECTED] [mailto:jboss- > [EMAIL PROTECTED]] On Behalf Of [EMAIL PROTECTED] > Sent: Thursday, October 03, 2002 4:48 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > > = > ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= > = > > JAVA VERSION DETAILS > java version "1.3.1_03" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03) > Java HotSpot(TM) Server VM (build 1.3.1_03-b03, mixed mode) > > = > > HERE ARE THE LAST 50 LINES OF THE LOG FILE > > [copy] Copying 1 file to /disk/orig/home/lubega/jbossro/jboss- > all/build/output/testbuild/client > [copy] Copying 1 file to /disk/orig/home/lubega/jbossro/jboss- > all/build/output/testbuild/lib > [copy] Copying 1 file to /disk/orig/home/lubega/jbossro/jboss- > all/build/output/testbuild/client > [copy] Copying 1 file to /disk/orig/home/lubega/jbossro/jboss- > all/build/output/testbuild/server/all/conf > [copy] Copying 1 file to /disk/orig/home/lubega/jbossro/jboss- > all/build/output/testbuild/server/all/deploy > > modules-most: > > partition-build: > [move] Moving 34 files to /disk/orig/home/lubega/jbossro/jboss- > all/build/output/testbuild/server/all/lib > [copy] Copying 112 files to /disk/orig/home/lubega/jbossro/jboss- > all/build/output/testbuild/server/default >[delete] Deleting 4 files from /disk/orig/home/lubega/jbossro/jboss- > all/build/output/testbuild/server/default/lib >[delete] Deleting 4 files from /disk/orig/home/lubega/jbossro/jboss- > all/build/output/testbuild/server/default/deploy >[delete] Deleting 1 files from /disk/orig/home/lubega/jbossro/jboss- > all/build/output/testbuild/server/default/conf > [mkdir] Created dir: /disk/orig/home/lubega/jbossro/jboss- > all/build/output/testbuild/server/minimal/deploy > [copy] Copying 3 files to /disk/orig/home/lubega/jbossro/jboss- > all/build/output/testbuild/server/minimal/conf > [move] Moving 1 files to /disk/orig/home/lubega/jbossro/jboss- > all/build/output/testbuild/server/minimal/conf > [copy] Copying 3 files to /disk/orig/home/lubega/jbossro/jboss- > all/build/output/testbuild/server/minimal/lib > [copy] Copying 1 file to /disk/orig/home/lubega/jbossro/jboss- > all/build/output/testbuild/server/minimal/deploy > [copy] Copying 1 file to /disk/orig/home/lubega/jbossro/jboss- > all/build/output/testbuild/server/minimal/lib > [mkdir] Created dir: /disk/orig/home/lubega/jbossro/jboss- > all/build/build > [unjar] Expanding: /disk/orig/home/lubega/jbossro/jboss- > all/build/output/testbuild/client/jboss-common-client.jar into > /disk/orig/home/lubega/jbossro/jboss-all/build/build > [unjar] Expanding: /disk/orig/home/lubega/jbossro/jboss- > all/build/output/testbuild/client/jboss-system-client.jar into > /disk/orig/home/lubega/jbossro/jboss-all/build/build > [unjar] Expanding: /disk/orig/home/lubega/jbossro/jboss- > all/build/output/testbuild/client/jboss-j2ee.jar into > /disk/orig/home/lubega/jbossro/jboss-all/build/build > [unjar] Expanding: /disk/orig/home/lubega/jbossro/jboss- > all/build/output/testbuild/client/jnp-client.jar into > /disk/orig/home/lubega/jbossro/jboss-all/build/build > [unjar] Expanding: /disk/orig/home/lubega/jbossro/jboss- > all/build/output/testbuild/client/jboss-jsr77-client.jar into > /disk/orig/home/lubega/jbossro/jboss-all/build/build > [unjar] Expanding: /disk/orig/home/lubega/jbossro/jboss- > all/build/output/testbuild/client/jboss-transaction-client.jar into > /disk/orig/home/lubega/jbossro/jboss-all/build/build > [unjar] Expanding: /disk/orig/home/lubega/jbossro/jboss- > all/build/output/testbuild/client/jboss-client.jar into > /disk/orig/home/lubega/jbossro/jboss-all/build/build > [unjar] Expanding: /disk/orig/home/lubega/jbossro/jboss- > all/build/output/testbuild/client/jmx-ejb-connector-client.jar into > /disk/orig/home/lubega/jbossro/jboss-all/build/build > [unjar] Expanding: /disk/orig/home/lubega/jbossro/jboss- > all/build/output/testbuild/client/jmx-connector-client-factory.jar into > /disk/orig/home/lubega/jbossro/jboss-all/build/build > [unjar] Expanding: /disk/orig/home/lubega/jbossro/jboss- > all/build/output/testbuild/client/jmx-rmi-connector-client.jar into > /disk/orig/home/lubega/jbossro/jboss-all/build/build > [unjar] Expanding: /disk/orig/home/lubega/jbossro/jboss- > all/build/output/testbuild/client/concurrent.jar into > /disk/orig/home/lubega/jbossro/jboss-all/build/build > [unjar] Expanding: /disk/orig/home/lubega/jbossro/jboss- > all/build/
RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
sorry.. forgot to add my renamed file. Should be fixed now. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of > [EMAIL PROTECTED] > Sent: Tuesday, September 17, 2002 7:45 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > > > = > ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= > = > > JAVA VERSION DETAILS > java version "1.3.1_03" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03) > Java HotSpot(TM) Server VM (build 1.3.1_03-b03, mixed mode) > > = > > HERE ARE THE LAST 50 LINES OF THE LOG FILE > > /disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss > /aspect/AspectClassLoader.java:165: cannot resolve symbol > symbol : class AspectDefinition > location: class org.jboss.aspect.AspectClassLoader > return (AspectDefinition) aspectDefinitions.get(clazz); > ^ --- Sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source & Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
FIXED, sorry. didn't do a build.clean so errors crept in. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of marc > fleury > Sent: Friday, August 16, 2002 10:25 AM > To: [EMAIL PROTECTED] > Subject: RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > > GUYS PLEASE, WHOEVER BROKE THE BUILD PLEASE FIX IT, > > marcf > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]] On > > Behalf Of [EMAIL PROTECTED] > > Sent: Friday, August 16, 2002 10:18 AM > > To: [EMAIL PROTECTED] > > Cc: [EMAIL PROTECTED] > > Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > > > > > > > = > > ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR > > DETAILS= > > = > > > > JAVA VERSION DETAILS > > java version "1.4.0_01" > > Java(TM) 2 Runtime Environment, Standard Edition (build > > 1.4.0_01-b03) Java HotSpot(TM) Client VM (build 1.4.0_01-b03, > > mixed mode) > > > > = > > > > HERE ARE THE LAST 50 LINES OF THE LOG FILE > > > > [xdoclet] Generating output for > > 'org.jboss.naming.NamingService' using template file > > 'jar:file:/disk/orig/home/lubega/jbossro/jboss-all/thirdparty/ > > xdoclet/xdoclet/lib/xdoclet.jar!/xdoclet/jmx/mbean.j'. > > [xdoclet] Generating output for > > 'org.jboss.web.AbstractWebContainer' using template file > > 'jar:file:/disk/orig/home/lubega/jbossro/jboss-all/thirdparty/ > > xdoclet/xdoclet/lib/xdoclet.jar!/xdoclet/jmx/mbean.j'. > > [xdoclet] Generating output for > > 'org.jboss.web.WebService' using template file > > 'jar:file:/disk/orig/home/lubega/jbossro/jboss-all/thirdparty/ > > xdoclet/xdoclet/lib/xdoclet.jar!/xdoclet/jmx/mbean.j'. > > > > compile-classes: > > [mkdir] Created dir: > > /disk/orig/home/lubega/jbossro/jboss-all/server/output/classes > > [javac] Compiling 513 source files to > > /disk/orig/home/lubega/jbossro/jboss-all/server/output/classes > > /disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/j > > boss/ejb/EnterpriseContext.java:11: warning: > > java.security.Identity in java.security has been deprecated > > import java.security.Identity; > > ^ > > /disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/j > > boss/ejb/EnterpriseContext.java:243: warning: > > java.security.Identity in java.security has been deprecated > > public Identity getCallerIdentity() > > ^ > > /disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/j > > boss/ejb/EnterpriseContext.java:369: warning: > > java.security.Identity in java.security has been deprecated > > public boolean isCallerInRole(Identity id) > > ^ > > /disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/j > > boss/security/SecurityDomain.java:12: warning: > > com.sun.net.ssl.KeyManagerFactory in com.sun.net.ssl has been > > deprecated import com.sun.net.ssl.KeyManagerFactory; > >^ > > /disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/j > > boss/security/SecurityDomain.java:13: warning: > > com.sun.net.ssl.TrustManagerFactory in com.sun.net.ssl has > > been deprecated import com.sun.net.ssl.TrustManagerFactory; > >^ > > /disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/j > > boss/security/SecurityDomain.java:32: warning: > > com.sun.net.ssl.KeyManagerFactory in com.sun.net.ssl has been > > deprecated > >public KeyManagerFactory getKeyManagerFactory() throws > > SecurityException; > > ^ > > /disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/j > > boss/security/SecurityDomain.java:38: warning: > > com.sun.net.ssl.TrustManagerFactory in com.sun.net.ssl has > > been deprecated > >public TrustManagerFactory getTrustManagerFactory() throws > > SecurityException; > > ^ > > /disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/j > > boss/ejb/MessageDrivenContainer.java:362: > > org.jboss.ejb.MessageDrivenContainer.ContainerInterceptor > > should be declared abstract; it does not define >
RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
GUYS PLEASE, WHOEVER BROKE THE BUILD PLEASE FIX IT, marcf > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On > Behalf Of [EMAIL PROTECTED] > Sent: Friday, August 16, 2002 10:18 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > > > = > ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR > DETAILS= > = > > JAVA VERSION DETAILS > java version "1.4.0_01" > Java(TM) 2 Runtime Environment, Standard Edition (build > 1.4.0_01-b03) Java HotSpot(TM) Client VM (build 1.4.0_01-b03, > mixed mode) > > = > > HERE ARE THE LAST 50 LINES OF THE LOG FILE > > [xdoclet] Generating output for > 'org.jboss.naming.NamingService' using template file > 'jar:file:/disk/orig/home/lubega/jbossro/jboss-all/thirdparty/ > xdoclet/xdoclet/lib/xdoclet.jar!/xdoclet/jmx/mbean.j'. > [xdoclet] Generating output for > 'org.jboss.web.AbstractWebContainer' using template file > 'jar:file:/disk/orig/home/lubega/jbossro/jboss-all/thirdparty/ > xdoclet/xdoclet/lib/xdoclet.jar!/xdoclet/jmx/mbean.j'. > [xdoclet] Generating output for > 'org.jboss.web.WebService' using template file > 'jar:file:/disk/orig/home/lubega/jbossro/jboss-all/thirdparty/ > xdoclet/xdoclet/lib/xdoclet.jar!/xdoclet/jmx/mbean.j'. > > compile-classes: > [mkdir] Created dir: > /disk/orig/home/lubega/jbossro/jboss-all/server/output/classes > [javac] Compiling 513 source files to > /disk/orig/home/lubega/jbossro/jboss-all/server/output/classes > /disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/j > boss/ejb/EnterpriseContext.java:11: warning: > java.security.Identity in java.security has been deprecated > import java.security.Identity; > ^ > /disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/j > boss/ejb/EnterpriseContext.java:243: warning: > java.security.Identity in java.security has been deprecated > public Identity getCallerIdentity() > ^ > /disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/j > boss/ejb/EnterpriseContext.java:369: warning: > java.security.Identity in java.security has been deprecated > public boolean isCallerInRole(Identity id) > ^ > /disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/j > boss/security/SecurityDomain.java:12: warning: > com.sun.net.ssl.KeyManagerFactory in com.sun.net.ssl has been > deprecated import com.sun.net.ssl.KeyManagerFactory; >^ > /disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/j > boss/security/SecurityDomain.java:13: warning: > com.sun.net.ssl.TrustManagerFactory in com.sun.net.ssl has > been deprecated import com.sun.net.ssl.TrustManagerFactory; >^ > /disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/j > boss/security/SecurityDomain.java:32: warning: > com.sun.net.ssl.KeyManagerFactory in com.sun.net.ssl has been > deprecated >public KeyManagerFactory getKeyManagerFactory() throws > SecurityException; > ^ > /disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/j > boss/security/SecurityDomain.java:38: warning: > com.sun.net.ssl.TrustManagerFactory in com.sun.net.ssl has > been deprecated >public TrustManagerFactory getTrustManagerFactory() throws > SecurityException; > ^ > /disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/j > boss/ejb/MessageDrivenContainer.java:362: > org.jboss.ejb.MessageDrivenContainer.ContainerInterceptor > should be declared abstract; it does not define > setConfiguration(org.w3c.dom.Element) in > org.jboss.ejb.Container.AbstractContainerInterceptor >class ContainerInterceptor >^ > /disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/j > boss/ejb/StatelessSessionContainer.java:560: > org.jboss.ejb.StatelessSessionContainer.ContainerInterceptor > should be declared abstract; it does not define > setConfiguration(org.w3c.dom.Element) in > org.jboss.ejb.Container.AbstractContainerInterceptor >class ContainerInterceptor >^ > /disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/j > boss/ejb/StatefulSessionContainer.java:754: > org.jboss.ejb.StatefulSessionContainer.ContainerInterceptor > should be declared abstract; it does not define > setConfiguration(org.w3c.dom.Element) in > org.jboss.ejb.Container.AbstractContainerInterceptor >class ContainerInterceptor >^ > /disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/j > boss/ejb/EntityContainer.java:1036: > org.jboss.ejb.EntityContainer.ContainerInterceptor should be > declared abstract; it does not define > setConfiguration(org.w3c.dom.Element) in > org.jboss.ejb.Container.AbstractContainerInterc
RE: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
Should be fixed now.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> [EMAIL PROTECTED]
> Sent: Monday, July 22, 2002 8:19 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
>
>
>
> =
> ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
> =
>
> JAVA VERSION DETAILS
> java version "1.4.0_01"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_01-b03)
> Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode)
>
> =
>
> HERE ARE THE LAST 50 LINES OF THE LOG FILE
>
>[javacc] Copyright (c) 1997-2000 Metamata, Inc.
>[javacc] (type "javacc" with no arguments for help)
>[javacc] Reading from file
> /disk/orig/home/lubega/jbossro/jboss-all/messaging/src/main/org/jb
> oss/mq/selectors/SelectorParser.jj . . .
>[javacc] Warning: Lookahead adequacy checking not being
> performed since option LOOKAHEAD is more than 1. Set option
> FORCE_LA_CHECK to true to force checking.
>[javacc] File "TokenMgrError.java" does not exist. Will create one.
>[javacc] File "ParseException.java" does not exist. Will create one.
>[javacc] File "Token.java" does not exist. Will create one.
>[javacc] File "ASCII_CharStream.java" does not exist. Will create one.
>[javacc] Parser generated with 0 errors and 1 warnings.
> [mkdir] Created dir:
> /disk/orig/home/lubega/jbossro/jboss-all/messaging/output/classes
> [javac] Compiling 8 source files to
> /disk/orig/home/lubega/jbossro/jboss-all/messaging/output/classes
>
> compile-classes:
> [javac] Compiling 165 source files to
> /disk/orig/home/lubega/jbossro/jboss-all/messaging/output/classes
> /disk/orig/home/lubega/jbossro/jboss-all/messaging/src/main/org/jb
> oss/mq/server/jmx/DestinationManager.java:44: cannot resolve symbol
> symbol : class DestinationManagerMBean
> location: class org.jboss.mq.server.jmx.DestinationManager
>implements DestinationManagerMBean
> ^
> /disk/orig/home/lubega/jbossro/jboss-all/messaging/src/main/org/jb
> oss/mq/server/jmx/InterceptorLoader.java:25: cannot resolve symbol
> symbol : class InterceptorLoaderMBean
> location: class org.jboss.mq.server.jmx.InterceptorLoader
>implements InterceptorLoaderMBean
> ^
> /disk/orig/home/lubega/jbossro/jboss-all/messaging/src/main/org/jb
> oss/mq/server/jmx/Invoker.java:25: cannot resolve symbol
> symbol : class InvokerMBean
> location: class org.jboss.mq.server.jmx.Invoker
>implements InvokerMBean
> ^
> /disk/orig/home/lubega/jbossro/jboss-all/messaging/src/main/org/jb
> oss/mq/server/jmx/Queue.java:29: cannot resolve symbol
> symbol : class QueueMBean
> location: class org.jboss.mq.server.jmx.Queue
>implements QueueMBean
> ^
> /disk/orig/home/lubega/jbossro/jboss-all/messaging/src/main/org/jb
> oss/mq/server/jmx/Topic.java:33: cannot resolve symbol
> symbol : class TopicMBean
> location: class org.jboss.mq.server.jmx.Topic
>implements TopicMBean
> ^
> /disk/orig/home/lubega/jbossro/jboss-all/messaging/src/main/org/jb
> oss/mq/server/jmx/DelayInterceptor.java:42: cannot resolve symbol
> symbol : class DelayInterceptorMBean
> location: class org.jboss.mq.server.jmx.DelayInterceptor
>implements DelayInterceptorMBean {
> ^
> 6 errors
>
> BUILD FAILED
> file:/disk/orig/home/lubega/jbossro/jboss-all/messaging/build.xml:
390: Compile failed; see the compiler error output for details.
Total time: 4 minutes 12 seconds
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
Hi, > BUILD FAILED > file:/disk/orig/home/lubega/jbossro/jboss-all/build/build.xml:1880: > Attribute names must not start with "<" characters. > Oops that was me - the problem is in my test area and not cvs - so no one else should get this. Chris = __ Do You Yahoo!? Yahoo! Autos - Get free new car price quotes http://autos.yahoo.com --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
Hi, --- Chris Kimpton <[EMAIL PROTECTED]> wrote: > > I'll have a look closer - only seems to be a problem for the jdk13 > build - the jdk14 build seems to be working fine... > I get this running it manually too (after clean checkout) - works for jdk14 and fails on NPE on zip stuff for jdk13 from IBM. For jdk131_03 from Sun, it gets further, but I then get a different error: most: [execmodules] == [execmodules] == Finished with 'most' in module 'transaction'. [execmodules] == [execmodules] _module-transaction-most: [mkdir] Created dir: /disk/orig/home/lubega/jbossro/jboss-all/build/output/jboss-3.1.0alpha/server/all/lib [copy] Copying 1 file to /disk/orig/home/lubega/jbossro/jboss-all/build/output/jboss-3.1.0alpha/server/all/lib [copy] Copying 1 file to /disk/orig/home/lubega/jbossro/jboss-all/build/output/jboss-3.1.0alpha/client [copy] Copying 1 file to /disk/orig/home/lubega/jbossro/jboss-all/build/output/jboss-3.1.0alpha/server/all/deploy [execmodules] == [execmodules] == Executing 'most' in module 'server'... [execmodules] == _buildmagic:init: configure: init: generate-parsers: [mkdir] Created dir: /disk/orig/home/lubega/jbossro/jboss-all/server/output/parsers/org/jboss/ejb/plugins/cmp/ejbql BUILD FAILED /disk/orig/home/lubega/jbossro/jboss-all/server/build.xml:382: Failed to launch JJTree I'll try rebooting the box later - maybe there is something system wide causing it a problem. Chris = __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com --- This sf.net email is sponsored by:ThinkGeek Caffeinated soap. No kidding. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
Hi, Nope - I turned on diskcheck after JBoss did that last time ;-) I'll have a look closer - only seems to be a problem for the jdk13 build - the jdk14 build seems to be working fine... Chris = __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com --- This sf.net email is sponsored by:ThinkGeek Caffeinated soap. No kidding. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
Is your disk full or something? I had the build to a clean checkout this morning and I'm not seeing any errors building main. Anyone else having a problem? Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, June 27, 2002 4:06 PM Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed > > = > ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= > = > > JAVA VERSION DETAILS > java version "1.3.0" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0) > Classic VM (build 1.3.0, J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)) > > = > > HERE ARE THE LAST 50 LINES OF THE LOG FILE > > > compile: > > jars: > [mkdir] Created dir: /disk/orig/home/lubega/jbossro/jboss-all/management/output/lib > [jar] Building jar: /disk/orig/home/lubega/jbossro/jboss-all/management/output/lib/jboss-jsr77.j ar > [jar] Building jar: /disk/orig/home/lubega/jbossro/jboss-all/management/output/lib/jboss-jsr77-c lient.jar > [jar] Building jar: /disk/orig/home/lubega/jbossro/jboss-all/management/output/lib/jboss-managem ent.jar > > BUILD FAILED > java.lang.NullPointerException > at org.apache.tools.zip.ZipOutputStream.finish(ZipOutputStream.java(Compiled Code)) > at java.util.zip.DeflaterOutputStream.close(DeflaterOutputStream.java:139) > at org.apache.tools.ant.taskdefs.Zip.execute(Zip.java) > at org.apache.tools.ant.Task.perform(Task.java) > at org.apache.tools.ant.Target.execute(Target.java) > at org.apache.tools.ant.Target.performTasks(Target.java) > at org.apache.tools.ant.Project.executeTarget(Project.java) > at org.jboss.tools.buildmagic.task.Ant.execute(Ant.java:261) > at org.jboss.tools.buildmagic.task.module.ExecuteModules.executeModule(ExecuteM odules.java:269) > at org.jboss.tools.buildmagic.task.module.ExecuteModules.execute(ExecuteModules .java:184) > at org.apache.tools.ant.Task.perform(Task.java) > at org.apache.tools.ant.Target.execute(Target.java) > at org.apache.tools.ant.Target.performTasks(Target.java) > at org.apache.tools.ant.Project.executeTarget(Project.java) > at org.apache.tools.ant.Project.executeTargets(Project.java) > at org.apache.tools.ant.Main.runBuild(Main.java) > at org.apache.tools.ant.Main.start(Main.java) > at org.apache.tools.ant.Main.main(Main.java) > --- This sf.net email is sponsored by:ThinkGeek Bringing you mounds of caffeinated joy. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
