Re: JDK 1.5 now running Gump...
On Wed, 13 Oct 2004, Adam R. B. Jack [EMAIL PROTECTED] wrote: Has someone made JDK 1.5 the default JVM for Gump?? We have a JDK 1.5 Gump. http://brutus.apache.org/gump/jdk15/ I think Niclas meant: Is the public Gump running JDK 1.5 (by accident) right now? The build failures of Crimson and Xerces-1 you can see in the log of the current(ly stalled) Gump run look as if it was the case. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JDK 1.5 now running Gump...
I think Niclas meant: Is the public Gump running JDK 1.5 (by accident) right now? Opps, ok. http://brutus.apache.org/gump/public/index.html shows: Java.version 1.4.2_05 and this ought'nt have change since Stefano updated it a week-ish ago. Also, I see this in their build: CLASSPATH :/opt/jdk1.4/lib/tools.jar The build failures of Crimson and Xerces-1 you can see in the log of the current(ly stalled) Gump run look as if it was the case. As such, hmm ... I can't explain this. regards, Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JDK 1.5 now running Gump...
On Wed, 13 Oct 2004, Niclas Hedhman [EMAIL PROTECTED] wrote: So, the only other explaination is that the xml-apis or something have brought DOM v3 into CVS/SVN, Doesn't look that way: http://cvs.apache.org/viewcvs.cgi/xml-commons/java/external/src/org/w3c/dom/Node.java last change is more than a year old. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JDK 1.5 now running Gump...
Java.version 1.4.2_05 This is from the LAST reasonably successful build - 76%. THEN something happened, and xerces and crimson doesn't build since they are somehow compiling against DOM v3, and not DOM v2. Good point, it is a run out of date. I'm waiting for cron to kick in to set the environment, and then we'll see. regards Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JDK 1.5 now running Gump...
Stefan Bodewig wrote: On Wed, 13 Oct 2004, Adam R. B. Jack [EMAIL PROTECTED] wrote: Has someone made JDK 1.5 the default JVM for Gump?? We have a JDK 1.5 Gump. http://brutus.apache.org/gump/jdk15/ I think Niclas meant: Is the public Gump running JDK 1.5 (by accident) right now? No, it's not. The build failures of Crimson and Xerces-1 you can see in the log of the current(ly stalled) Gump run look as if it was the case. I have changed the crontab last night to do this: 0:00 - public [jdk1.4 + gump/live + nagging] 3:00 - public [jdk1.4 + gump/live] 6:00 - jdk15 [jdk1.5 + gump/live] 9:00 - public [jdk1.4 + gump/live] 12:00 - test [jdk1.4 + gump/trunk] 15:00 - public [jdk1.4 + gump/live] 18:00 - kaffe [kaffe + gump/live] 21:00 - public [jdk1.4 + gump/live] I'm giving 3 hours now since I had the impression that builds were starting to overlap. -- Stefano. smime.p7s Description: S/MIME Cryptographic Signature
Re: Kaffe? [was Re: JDK 1.5 now running Gump...]
Adam R. B. Jack wrote: Ok, I've made the gump/cron/local-env-brutus.sh put the chosen JDK at the front of the path (it was at the end.) export JAVA_HOME=/opt/jdk1.4 export PATH=$JAVA_HOME/bin:$PATH This seems to cure things, for now: http://brutus.apache.org/gump/test/buildLog.html regards, a, yes! damn, sorry people, the kaffe vm was installed by apt-get so it went in the default path and since they have a java symlink I think that's what happened. I will ge rid of those symlinks. sorry about that (but I guess, only those who don't do anything don't break anything ;-) -- Stefano. smime.p7s Description: S/MIME Cryptographic Signature
Re: JDK 1.5 now running Gump...
On Thursday 14 October 2004 01:12, Stefano Mazzocchi wrote: I'm giving 3 hours now since I had the impression that builds were starting to overlap. Perhaps not enough :o( Last log says ; 3 hours 7 minutes. Start Date/Time (UTC) Tue, 12 Oct 2004 19:02:00 (UTC) End Date/Time (UTC) Tue, 12 Oct 2004 22:09:10 (UTC) -- +--//---+ / http://www.bali.ac/ / http://niclas.hedhman.org / +--//---+ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Kaffe? [was Re: JDK 1.5 now running Gump...]
sorry about that (but I guess, only those who don't do anything don't break anything ;-) Precisely. No problem, no apology needed.. regards Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JDK 1.5 now running Gump...
Niclas Hedhman wrote: On Thursday 14 October 2004 01:12, Stefano Mazzocchi wrote: I'm giving 3 hours now since I had the impression that builds were starting to overlap. Perhaps not enough :o( Last log says ; 3 hours 7 minutes. Start Date/Time (UTC) Tue, 12 Oct 2004 19:02:00 (UTC) End Date/Time (UTC) Tue, 12 Oct 2004 22:09:10 (UTC) few minutes overlap is fine, an hour is not. Also note that those 3 hours will be much reduced now that overlap is reduced. gump is disk-bound and I think the overlap was causing massive delays. since we have two disks and 4 processors, we should start thinking about moving workspaces in the two disks. -- Stefano. smime.p7s Description: S/MIME Cryptographic Signature
Re: JDK 1.5
Adam R. B. Jack wrote: How do we get the word out about the JDK 1.5 Gump runs? http://brutus.apache.org/gump/jdk15/ Teams may not be shooting for JDK1.5 compliance right now, but if Gump could do the leg work for them, maybe they'd do minor tweaks if needed. I could see this help user, but I feel it has to start sooner, not later (so no releases go out w/ minor JDK1.5 nits if could be avoided). Ought we consider notifications? Other ideas? The way I did this in prior releases was to build it without notification, and then personally approach the projects which had failures. I kept a catalog of problems encountered which I dutifully submitted to Sun (who had made public claims about being 100% backwards compatible - bunk!). These problems were, of course, summarily ignored. My experience was that projects by and large were extremely appreciative of being given specific and human feedback, and I found the process to be very rewarding. Still, in the case of 1.4, there was a gap of six months to a year before everyone felt confortable with making it official. - Sam Ruby - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JDK 1.5
Yeah, there is something so rewarding about the 'thank you' one gets 99% of the time. Human feedback it is. Thanks. regards, Adam - Original Message - From: Sam Ruby [EMAIL PROTECTED] To: Gump code and data [EMAIL PROTECTED] Sent: Wednesday, July 21, 2004 6:20 PM Subject: Re: JDK 1.5 Adam R. B. Jack wrote: How do we get the word out about the JDK 1.5 Gump runs? http://brutus.apache.org/gump/jdk15/ Teams may not be shooting for JDK1.5 compliance right now, but if Gump could do the leg work for them, maybe they'd do minor tweaks if needed. I could see this help user, but I feel it has to start sooner, not later (so no releases go out w/ minor JDK1.5 nits if could be avoided). Ought we consider notifications? Other ideas? The way I did this in prior releases was to build it without notification, and then personally approach the projects which had failures. I kept a catalog of problems encountered which I dutifully submitted to Sun (who had made public claims about being 100% backwards compatible - bunk!). These problems were, of course, summarily ignored. My experience was that projects by and large were extremely appreciative of being given specific and human feedback, and I found the process to be very rewarding. Still, in the case of 1.4, there was a gap of six months to a year before everyone felt confortable with making it official. - Sam Ruby - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JDK 1.5
Hi Adam, a quick Google search concerning this problem brought me to this link : http://forum.java.sun.com/thread.jsp?thread=522017forum=316message=2500873 What I understand, is that the problem means that we are trying to run under JDK 1.4 some code compiled under JDK 1.5. These options of javac : -source 1.5 -target jsr14 according to the article, allow to compile under jdk1.5 and to run under jdk1.4. Cheers, Antoine Adam R. B. Jack wrote: The CleanUp branch is getting pretty darn close to matching the CVS HEAD Gump again (the odd 'didn't expand @@DATE@@ somewhere obscure' kinda bug might exist, but not in the first projects, or so this seems to show: http://gump.try.sybase.com/buildLog.html). However, we get this w/ CleanUp running on JDK1.5: http://brutus.apache.org/gump/jdk15/xml-crimson/xml-crimson/gump_work/build_xml-crimson_xml-crimson.html#Output Exception in thread main java.lang.UnsupportedClassVersionError: org/apache/tools/ant/Main (Unsupported major.minor version 49.0) I suspect that this means that (1) the JDK 1.5 compiler was found/used by bootstrap-ant and and (2) the JDK 1.4 compiler was found/used by Ant and does not grok JDK 1.5 classes. Just a guess. Any thoughts on how we tighten things up in an environment where we have multiple compilers/JDKs installed? Can we get Ant to (tersely) tell us which compiler it has found and is using? Ought we try to tell Ant? The story this tells, is confused (at best): http://brutus.apache.org/gump/jdk15/environment.html#Annotations http://brutus.apache.org/gump/jdk15/environment.html#Tail+of+CheckEnvironment+%3A+check_java_compiler Thanks in advance. regards, Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JDK 1.5
Thanks, but our goal is to work completely in JDK1.5, so the task is to either tighten our environment (to make JDK 1.4 simply not available to the JDK 1.5 run) or to be more explicit/careful in Gump code (and bootstrap scripts). I suspect the latter has the better long-term mileage, but I don't know the best approach (for launching JDK compiler, and/or for Ant). [We've had a need to have tools.jar on the CLASSPATH, so Ant can find a compiler, which kinda goes against the purpose of Gump, and it setting CLASSPATH. This is a JIRA entry I'd like to close.] FWIIW: I'm facing similar w/ moving to Python 2.3 (and on some platforms I need to check for 'python2.3' executable prior to 'python'). This is easier since the scripts are more in my direct control. regards, Adam - Original Message - From: Antoine Levy-Lambert [EMAIL PROTECTED] To: Gump code and data [EMAIL PROTECTED] Sent: Friday, July 02, 2004 8:34 AM Subject: Re: JDK 1.5 Hi Adam, a quick Google search concerning this problem brought me to this link : http://forum.java.sun.com/thread.jsp?thread=522017forum=316message=2500873 What I understand, is that the problem means that we are trying to run under JDK 1.4 some code compiled under JDK 1.5. These options of javac : -source 1.5 -target jsr14 according to the article, allow to compile under jdk1.5 and to run under jdk1.4. Cheers, Antoine Adam R. B. Jack wrote: The CleanUp branch is getting pretty darn close to matching the CVS HEAD Gump again (the odd 'didn't expand @@DATE@@ somewhere obscure' kinda bug might exist, but not in the first projects, or so this seems to show: http://gump.try.sybase.com/buildLog.html). However, we get this w/ CleanUp running on JDK1.5: http://brutus.apache.org/gump/jdk15/xml-crimson/xml-crimson/gump_work/build _xml-crimson_xml-crimson.html#Output Exception in thread main java.lang.UnsupportedClassVersionError: org/apache/tools/ant/Main (Unsupported major.minor version 49.0) I suspect that this means that (1) the JDK 1.5 compiler was found/used by bootstrap-ant and and (2) the JDK 1.4 compiler was found/used by Ant and does not grok JDK 1.5 classes. Just a guess. Any thoughts on how we tighten things up in an environment where we have multiple compilers/JDKs installed? Can we get Ant to (tersely) tell us which compiler it has found and is using? Ought we try to tell Ant? The story this tells, is confused (at best): http://brutus.apache.org/gump/jdk15/environment.html#Annotations http://brutus.apache.org/gump/jdk15/environment.html#Tail+of+CheckEnvironme nt+%3A+check_java_compiler Thanks in advance. regards, Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JDK 1.5
On Fri, 2 Jul 2004, Adam R. B. Jack [EMAIL PROTECTED] wrote: http://brutus.apache.org/gump/jdk15/xml-crimson/xml-crimson/gump_work/build_xml-crimson_xml-crimson.html#Output I get an internal server error when I try to access this. Exception in thread main java.lang.UnsupportedClassVersionError: org/apache/tools/ant/Main (Unsupported major.minor version 49.0) Most probably means that bootstrap-ant has been built by JDK 1.5, while the Java VM running Ant when building Crimson is JDK 1.4. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JDK 1.5
On Fri, 2 Jul 2004, Adam R. B. Jack [EMAIL PROTECTED] wrote: http://brutus.apache.org/gump/jdk15/xml-crimson/xml-crimson/gump_work/build_xml-crimson_xml-crimson.html#Output I get an internal server error when I try to access this. Yes, I foolishly tried to remove an xdocs related bug before I went away for the long weekend, and trashed it. Working to restore, sorry... Exception in thread main java.lang.UnsupportedClassVersionError: org/apache/tools/ant/Main (Unsupported major.minor version 49.0) Most probably means that bootstrap-ant has been built by JDK 1.5, while the Java VM running Ant when building Crimson is JDK 1.4. Agreed, now how do we work w/ Ant to ensure this does not happen? Also, if you see then env page (when it comes back) just launching Java seems to give JDK1.4. regards Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JDK 1.5
On Fri, 2 Jul 2004, Adam R. B. Jack [EMAIL PROTECTED] wrote: Agreed, now how do we work w/ Ant to ensure this does not happen? Also, if you see then env page (when it comes back) just launching Java seems to give JDK1.4. Hmm, while we wait for the env page to come back 8-) boostrap-ant will probably pick up tools.jar from the CLASSPATH, but this shouldn't be necessary as the script can find it on its own if JAVA_HOME is set correctly. I have no idea how you launch java from Python. This one obviously does not use the 1.5 JDK. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JDK 1.5
http://brutus.apache.org/gump/jdk15/xml-crimson/xml-crimson/gump_work/build_xml-crimson_xml-crimson.html#Output I get an internal server error when I try to access this. Yes, I foolishly tried to remove an xdocs related bug before I went away for the long weekend, and trashed it. Working to restore, sorry... Ought be back. regards Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JDK 1.5
boostrap-ant will probably pick up tools.jar from the CLASSPATH, but this shouldn't be necessary as the script can find it on its own if JAVA_HOME is set correctly. For some reason I didn't beleive that to be the case (back when I added the usage of the system CLASSPATH w/ tools in it.) I've not checked in a long time. You feeling game to try a copy of Gumpy (again) to see if you can investigate for us? No pressure, but clearly I failed to figure it out eons ago. I have no idea how you launch java from Python. This one obviously does not use the 1.5 JDK. It simple makes a system call to 'java', so it gets what is first on the path. BTW: I just remembered ... I think the gump (user account) profile includes the local-env-py.sh from public! This was added back when there was only one (FWIIW: not by me, or I'd've remembered sooner). I don't think this is needed, nor wanted -- and is likely a problem. I don't know if cron worked without that, but I think it should. I'll comment out, and hope I don't dork things up before I go away. This was in ~/.bash_profile and is now commented out: # For now we only have one Gump running, so # we can take values from it. #. /usr/local/gump/public/gump/local-env-py-brutus.sh regards, Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JDK 1.5
I have no idea how you launch java from Python. This one obviously does not use the 1.5 JDK. It simple makes a system call to 'java', so it gets what is first on the path. Ah yes, the PATH is visible here: http://brutus.apache.org/gump/public/gump_work/check_env.html and http://brutus.apache.org/gump/jdk15/gump_work/check_env.html Currently JDK15 shows: PATH=/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games:/usr/local/j2sdk1. 4.2_04/bin:/usr/local/gump/forrest/bin:/usr/local/gump/maven-1.0-rc3/bin:/us r/local/jdk1.5.0/bin:/usr/local/gump/maven-1.0-rc3/bin w/ JDK1.4 earlier in path.Let me try a run w/o that (exit the shell I am in and re-enter).Yup, better: http://brutus.apache.org/gump/jdk15/gump_work/check_env.htmlI tried using threads --- and got CVS errors -- hmm, so some work to do.I've turned them off, and we are making some progress:http://brutus.apache.org/gump/jdk15/buildLog.htmlregards Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
