Re: mx4j in gump
On Nov 16, 2006, at 3:39 PM, Antoine Levy-Lambert wrote: I do not understand why mx4j keeps failing. Apparently we still can't see the fix. The fix of Simon is visible here : http://mx4j.cvs.sourceforge.net/mx4j/mx4j/build/build.xml? revision=1.115view=markup Is the source code that we see through this web interface not the same as the one that gump downloads by cvs update ? As we learn, one of these CVS repositories is not like the other. This is the wc on my own laptop: [EMAIL PROTECTED] build $ cvs status build.xml === File: build.xml Status: Up-to-date Working revision:1.114 Repository revision: 1.114 /cvsroot/mx4j/mx4j/build/build.xml,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) And yes, still borken. Yes, it's frustrating. I hope we never get so big that we run into something like this. Of course, we're on a slightly more modern version control system. S. -- [EMAIL PROTECTED]http://www.temme.net/sander/ PGP FP: 51B4 8727 466A 0BC3 69F4 B7B8 B2BE BC40 1529 24AF smime.p7s Description: S/MIME cryptographic signature
build of mx4j in gump
Hi, Simon Bordet has updated the source code of mx4j so that there are no build errors, but the CVS update on vmgump [1] does not work: Command Line cvs -q -z3 -d :pserver:[EMAIL PROTECTED]:/cvsroot/mx4j update -P -d -A Output Fatal error, aborting. anoncvs_mx4j: no such system user Can someone try to fix this ? Regards, Antoine [1] http://vmgump.apache.org/gump/public/mx4j/gump_work/update_mx4j.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: build of mx4j in gump
Hm... On Nov 15, 2006, at 6:33 AM, Antoine Levy-Lambert wrote: Hi, Simon Bordet has updated the source code of mx4j so that there are no build errors, but the CVS update on vmgump [1] does not work: Command Line cvs -q -z3 -d :pserver:[EMAIL PROTECTED]:/cvsroot/ mx4j update -P -d -A Output Fatal error, aborting. anoncvs_mx4j: no such system user Sounds like good old SF brokenness to me... Can someone try to fix this ? I had the same error on Clarus, so I blew away my login info. Got a couple of 'Connection Refused' errors when trying to re-login from both Clarus and my home laptop, but a couple of minutes later it went through. No joy building it though: [EMAIL PROTECTED] build $ sh ./build.sh Buildfile: build.xml flags: jdk14-present: jaas-present: javamail-present: [echo] JavaMail classes are not present, therefore the SMTP MBean will not be built. [echo] You need mail.jar and activation.jar in the MX4J lib directory. [echo] You can download them from http://java.sun.com/products/ javamail jython-present: [echo] Jython classes are not present, therefore the JythonRunner MBean will not be built. [echo] You need jython.jar in the MX4J lib directory [echo] You can download it from http://www.jython.org jetty-present: compile.jmx: [mkdir] Created dir: /Volumes/Files/projects/mx4j/classes/core [mkdir] Created dir: /Volumes/Files/projects/mx4j/dist/lib [javac] Compiling 230 source files to /Volumes/Files/projects/ mx4j/classes/core [javac] /Volumes/Files/projects/mx4j/src/core/mx4j/server/ ChainedMBeanServer.java:124: warning: [deprecation] deserialize (javax.management.ObjectName,byte[]) in javax.management.MBeanServer has been deprecated [javac]public ObjectInputStream deserialize(ObjectName objectName, byte[] bytes) [javac] ^ [javac] /Volumes/Files/projects/mx4j/src/core/mx4j/server/ ChainedMBeanServer.java:112: warning: [deprecation] deserialize (java.lang.String,byte[]) in javax.management.MBeanServer has been deprecated [javac]public ObjectInputStream deserialize(String className, byte[] bytes) [javac] ^ [javac] /Volumes/Files/projects/mx4j/src/core/mx4j/server/ ChainedMBeanServer.java:118: warning: [deprecation] deserialize (java.lang.String,javax.management.ObjectName,byte[]) in javax.management.MBeanServer has been deprecated [javac]public ObjectInputStream deserialize(String className, ObjectName loaderName, byte[] bytes) [javac] ^ [javac] /Volumes/Files/projects/mx4j/src/core/mx4j/server/ ChainedMBeanServer.java:115: warning: [deprecation] deserialize (java.lang.String,byte[]) in javax.management.MBeanServer has been deprecated [javac] return getMBeanServer().deserialize(className, bytes); [javac]^ [javac] /Volumes/Files/projects/mx4j/src/core/mx4j/server/ ChainedMBeanServer.java:121: warning: [deprecation] deserialize (java.lang.String,javax.management.ObjectName,byte[]) in javax.management.MBeanServer has been deprecated [javac] return getMBeanServer().deserialize(className, loaderName, bytes); [javac]^ [javac] /Volumes/Files/projects/mx4j/src/core/mx4j/server/ ChainedMBeanServer.java:127: warning: [deprecation] deserialize (javax.management.ObjectName,byte[]) in javax.management.MBeanServer has been deprecated [javac] return getMBeanServer().deserialize(objectName, bytes); [javac]^ [javac] /Volumes/Files/projects/mx4j/src/core/mx4j/server/ MX4JMBeanServer.java:335: warning: [deprecation] deserialize (javax.management.ObjectName,byte[]) in javax.management.MBeanServer has been deprecated [javac]public ObjectInputStream deserialize(ObjectName objectName, byte[] bytes) [javac] ^ [javac] /Volumes/Files/projects/mx4j/src/core/mx4j/server/ MX4JMBeanServer.java:315: warning: [deprecation] deserialize (java.lang.String,byte[]) in javax.management.MBeanServer has been deprecated [javac]public ObjectInputStream deserialize(String className, byte[] bytes) [javac] ^ [javac] /Volumes/Files/projects/mx4j/src/core/mx4j/server/ MX4JMBeanServer.java:294: warning: [deprecation] deserialize (java.lang.String,javax.management.ObjectName,byte[]) in javax.management.MBeanServer has been deprecated [javac]public ObjectInputStream deserialize(String className, ObjectName loaderName, byte[] bytes) [javac] ^ [javac] 9 warnings BUILD FAILED /Volumes/Files/projects/mx4j/build/build.xml:233: Manifest file: / Volumes/Files/projects/mx4j/src/etc/MANIFEST.MF does not exist. Total time: 17 seconds [EMAIL PROTECTED] build $ echo $JAVA_HOME /Library/Java/Home This is the
Re: build of mx4j in gump
Hello Sander, Simon Bordet wrote me that he fixed it. He did change the build.xml 8 hours ago. http://mx4j.cvs.sourceforge.net/mx4j/mx4j/build/build.xml?view=log so maybe vmgump should be repaired too so that the mx4j update can happen. Regards, Antoine Original-Nachricht Datum: Wed, 15 Nov 2006 08:29:26 -0800 Von: Sander Temme [EMAIL PROTECTED] An: Gump code and data general@gump.apache.org Betreff: Re: build of mx4j in gump Hm... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: build of mx4j in gump
On Nov 15, 2006, at 12:59 PM, Antoine Levy-Lambert wrote: Simon Bordet wrote me that he fixed it. He did change the build.xml 8 hours ago. http://mx4j.cvs.sourceforge.net/mx4j/mx4j/build/build.xml?view=log so maybe vmgump should be repaired too so that the mx4j update can happen. My wc doesn't see that revision. Could this be one of those cases where the general public doesn't get to see the results of a commit until a particular sync happens? In that case, we'll see it coming down the pike. I don't have rights on vmgump, so I can't help you there. But Clarus is completing its update and breaking on the build. S. -- [EMAIL PROTECTED]http://www.temme.net/sander/ PGP FP: 51B4 8727 466A 0BC3 69F4 B7B8 B2BE BC40 1529 24AF smime.p7s Description: S/MIME cryptographic signature
Re: build of mx4j in gump
Sander Temme wrote: I don't have rights on vmgump, so I can't help you there. we should fix that. thoughts anybody? -- Stefano. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: build of mx4j in gump
On Wed, 15 Nov 2006, Antoine Levy-Lambert [EMAIL PROTECTED] wrote: Hello Sander, Simon Bordet wrote me that he fixed it. He did change the build.xml 8 hours ago. http://mx4j.cvs.sourceforge.net/mx4j/mx4j/build/build.xml?view=log There is a delay between a change happening in committer CVS and it becoming available on public CVS at sourceforge, They use two different CVS repositories and sync them (later rather than sooner). There isn't much we can do at our side other than wait. I just did a cvs up on vmgump manually without any problems - and without receiving any changes. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Mx4j-devel] MX4J and Gump (and another log4j deprecation effect)
On Tuesday 25 May 2004 15:23, Bordet, Simone wrote: The only thing I'd prefer to avoid is to make our build running against the latest CVS (which are usually unstable), since this is gump's job. You should build and release against the latest stable Log4J, no doubt. If Log4J removed deprecated API, fine for all, but I'd prefer to wait for a stable release of Log4J before modifying MX4J's build. What you need to do is to change your codebase to use the newer Level and Logger instead of Priority and Category, which has been around since 1.2.0. Log4J mistakenly also removed the RootCategory and replaced with a RootLevel, but there were no interim 'deprecated' period, so after Avalon was affected by the change the RootCategory was re-introduced in their codebase. So, 1. You change your codebase. 2. If you release, you can build and release against/together with Log4J 1.2.8 3. Such release will also work with Log4J 'next release'. 4. Such change will make Gump happy :o) Cheers Niclas -- +--//---+ / http://www.bali.ac/ / http://niclas.hedhman.org / +--//---+ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Mx4j-devel] MX4J and Gump (and another log4j deprecation effect)
From time to time we get an email similar to this one, and we try to promptly fix the build. Thanks, that is aprpeciated, so mind if automate that? This entry will do it. nag from=Simone Bordet lt;[EMAIL PROTECTED]gt; to=[EMAIL PROTECTED]/ I am in a busy period now, but I'll try to get the build going as soon as I can, running against the latest stable Log4J (which I thought we were already doing, against 1.2.8 if I remember well). Yup, that is correct. This notification is a warning for their upcoming release, giving you time to get ahead of the game. You ought have some time. The only thing I'd prefer to avoid is to make our build running against the latest CVS (which are usually unstable), since this is gump's job. 100% agreed. If Log4J removed deprecated API, fine for all, but I'd prefer to wait for a stable release of Log4J before modifying MX4J's build. If you think there is a better approach, please let me know. Niclas' suggestions are spot on. That fix is the right way for MX4J to 'play nicely' with the widest/most used range of released log4j's (including the up coming one). [Log4j did a good job of making Level and Priority available two years before they removed the deprecated classes.] (I believe your use case is a simple one, with no binary compatible issues.) Thanks for being patient with deprecated APIs. Thanks for using Apache software. regards, Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
MX4J and Gump (and another log4j deprecation effect)
Hi, I don't know if you are aware of Apache Gump, but it is a continuous integration tool. See: http://gump.apache.org MX4J has an entry, which means it gets compiled against the very latest (CVS HEAD, SVN trunk) of it's dependencies (when possible.) See: http://brutus.apache.org:8080/gump/mx4j/mx4j/index.html Recently your entry started failing, and I'm writing to inform you of this (and ask if you'd like ongoing notifications). Would you mind if we send notification mails (when builds start failing) to this list? We can pick what address the mails appear to come from. BTW: These look like another victim of the recent log4j deprecations: http://brutus.apache.org:8080/gump/mx4j/mx4j/gump_work/build_mx4j_mx4j.txt see: http://gump.chalko.com/gb/blog/SuccessStories/?permalink=Log4J-CL-EL-JV.txtpreview=truesmm=y regards, Adam -- Experience the Unwired Enterprise: http://www.sybase.com/unwiredenterprise Try Sybase: http://www.try.sybase.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
