RE: [JBoss-dev] stop using JDK 1.4 for development
I'm working on an automated script to get and build from source, run the testsuite and post the results. It's about 90% complete - isn't everything? I expect to use it internally for testing on various os/jvm combinations. And, with a little luck, establish a site to post the results and collect results for other combinations from external sources. The bad news is that it currently includes a few hacks to cope with some quirks in the build system; see bugs 682352 and 667825. Rod -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Bill Burke Sent: Friday, February 28, 2003 11:27 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] stop using JDK 1.4 for development chris kimptons builds are perfect, but definately not useless. I'll be setting up a nightly build as soon as I get my new machine. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jason Dillon Sent: Friday, February 28, 2003 10:53 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] stop using JDK 1.4 for development Any automated build and reporting system would be valuable... just depends on the implementation as to whether it is useful or not. --jason On Friday, February 28, 2003, at 10:36 PM, David Jencks wrote: On 2003.02.28 10:23 Jeff Haynie wrote: The problem really is with me - I fess up. Bill's mad because I broke the build twice this week by inadvertantly checking in code (throwing an exception that is the new overloaded version in 1.4) that only compiles on 1.4. Unfortunately, my whole work and home environment *DO* require 1.4 and only works under 1.4 - so I sometimes forget to re-set my path to JDK1.3 when I compile. So, it compiles fine under 1.4. I'm changing my jboss build environment to force my path and JDK to 1.3 before it runs. Maybe be can update the build.bat/.sh to automatically do this (or at least check the version before you compile) and that would fix this problem for everyone? I don't think this is viable, since some features are simply going to be supported only on jdk 1.4. The primary example is working/reasonable transaction logging: I think non-blocking sockets versions of transport will be another example. I really think a reliable warning service is the way to go. I found Chris Kimpton's compilation reports so unreliable I stopped paying attention to them a long time ago. Are they useful to anyone? david -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Jencks Sent: Friday, February 28, 2003 10:16 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] stop using JDK 1.4 for development I'd prefer to have a reliable way to report these problems, since I don't consider it realistic for me to develop on 1.3.1. How do you detect them? For the particular problem of nested exceptions, I think we should always use the jboss NestedThrowable stuff Jason wrote since it provides a much more reasonable stack trace. Dain and I made as much as we could find of the jca and jta frameworks use this with good results. How could we make this better known and popularize it? thanks david jencks On 2003.02.28 08:42 Bill Burke wrote: There have been a lot of build breakages lately because people are using JDK 1.4 features and they break in JDK 1.3 builds. WE STILL SUPPORT JDK 1.3. My suggestion? Stop developing JBOss with jdk 1.4 and develop with 1.3. Please stop the sloppiness. Bill --- 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
RE: [JBoss-dev] stop using JDK 1.4 for development
Bill, I thought JBoss was going to support 1.4. Is this not the case? - Matt -Original Message- From: Bill Burke [mailto:[EMAIL PROTECTED] Sent: Fri 2/28/2003 8:42 AM To: Jboss-Dev Cc: Subject: [JBoss-dev] stop using JDK 1.4 for development There have been a lot of build breakages lately because people are using JDK 1.4 features and they break in JDK 1.3 builds. WE STILL SUPPORT JDK 1.3. My suggestion? Stop developing JBOss with jdk 1.4 and develop with 1.3. Please stop the sloppiness. Bill --- 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 winmail.dat
RE: [JBoss-dev] stop using JDK 1.4 for development
Title: [JBoss-dev] stop using JDK 1.4 for development We're not going to have .jpp or other ant switches just so that people can use nested exceptions -Original Message-From: Matt Munz [mailto:[EMAIL PROTECTED]On Behalf Of Matt MunzSent: Friday, February 28, 2003 8:54 AMTo: [EMAIL PROTECTED]Subject: RE: [JBoss-dev] stop using JDK 1.4 for development Bill, I thought JBoss was going to support 1.4. Is this not the case? - Matt -Original Message- From: Bill Burke [mailto:[EMAIL PROTECTED] Sent: Fri 2/28/2003 8:42 AM To: Jboss-Dev Cc: Subject: [JBoss-dev] stop using JDK 1.4 for development There have been a lot of build breakages lately because people are using JDK1.4 features and they break in JDK 1.3 builds. WE STILL SUPPORT JDK 1.3.My suggestion? Stop developing JBOss with jdk 1.4 and develop with 1.3.Please stop the sloppiness.Bill---This sf.net email is sponsored by:ThinkGeekWelcome to geek heaven.http://thinkgeek.com/sf___Jboss-development mailing list[EMAIL PROTECTED]https://lists.sourceforge.net/lists/listinfo/jboss-development attachment: winmail.dat
RE: [JBoss-dev] stop using JDK 1.4 for development
What's the reason to support JDK1.3 -- just asking, not against it. We've been using 1.4.1 for a good while now and it seems to be much better in performance and stability. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of danch Sent: Friday, February 28, 2003 9:30 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] stop using JDK 1.4 for development There's a big difference between supporting 1.4 and _not_ supporting 1.3 Matt Munz wrote: Bill, I thought JBoss was going to support 1.4. Is this not the case? - Matt -Original Message- From: Bill Burke [mailto:[EMAIL PROTECTED] Sent: Fri 2/28/2003 8:42 AM To: Jboss-Dev Cc: Subject: [JBoss-dev] stop using JDK 1.4 for development There have been a lot of build breakages lately because people are using JDK 1.4 features and they break in JDK 1.3 builds. WE STILL SUPPORT JDK 1.3. My suggestion? Stop developing JBOss with jdk 1.4 and develop with 1.3. Please stop the sloppiness. Bill --- 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] stop using JDK 1.4 for development
The real question is: Does JBoss _require_ 1.4? I hope the answer will be 'no'. bax Am Freitag, 28.02.03, um 15:36 Uhr (Europe/Budapest) schrieb Jeff Haynie: What's the reason to support JDK1.3 -- just asking, not against it. We've been using 1.4.1 for a good while now and it seems to be much better in performance and stability. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of danch Sent: Friday, February 28, 2003 9:30 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] stop using JDK 1.4 for development There's a big difference between supporting 1.4 and _not_ supporting 1.3 Matt Munz wrote: Bill, I thought JBoss was going to support 1.4. Is this not the case? - Matt -Original Message- From: Bill Burke [mailto:[EMAIL PROTECTED] Sent: Fri 2/28/2003 8:42 AM To: Jboss-Dev Cc: Subject: [JBoss-dev] stop using JDK 1.4 for development There have been a lot of build breakages lately because people are using JDK 1.4 features and they break in JDK 1.3 builds. WE STILL SUPPORT JDK 1.3. My suggestion? Stop developing JBOss with jdk 1.4 and develop with 1.3. Please stop the sloppiness. Bill --- 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] stop using JDK 1.4 for development
no, jboss doesn't require 1.4. And yes we must support 1.3 because of people that are using JBoss in production with JDK 1.3 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Holger Baxmann Sent: Friday, February 28, 2003 9:48 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] stop using JDK 1.4 for development The real question is: Does JBoss _require_ 1.4? I hope the answer will be 'no'. bax Am Freitag, 28.02.03, um 15:36 Uhr (Europe/Budapest) schrieb Jeff Haynie: What's the reason to support JDK1.3 -- just asking, not against it. We've been using 1.4.1 for a good while now and it seems to be much better in performance and stability. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of danch Sent: Friday, February 28, 2003 9:30 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] stop using JDK 1.4 for development There's a big difference between supporting 1.4 and _not_ supporting 1.3 Matt Munz wrote: Bill, I thought JBoss was going to support 1.4. Is this not the case? - Matt -Original Message- From: Bill Burke [mailto:[EMAIL PROTECTED] Sent: Fri 2/28/2003 8:42 AM To: Jboss-Dev Cc: Subject: [JBoss-dev] stop using JDK 1.4 for development There have been a lot of build breakages lately because people are using JDK 1.4 features and they break in JDK 1.3 builds. WE STILL SUPPORT JDK 1.3. My suggestion? Stop developing JBOss with jdk 1.4 and develop with 1.3. Please stop the sloppiness. Bill --- 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] stop using JDK 1.4 for development
Bill, JRE 1.4. I don't care how you compile. I just want to make sure that running JBoss under 1.4 (which is what I'm doing now) is supported. - Matt -Original Message- From: [EMAIL PROTECTED] on behalf of Bill Burke Sent: Fri 2/28/2003 9:18 AM To: [EMAIL PROTECTED] Cc: Subject: RE: [JBoss-dev] stop using JDK 1.4 for development We're not going to have .jpp or other ant switches just so that people can use nested exceptions -Original Message- From: Matt Munz [mailto:[EMAIL PROTECTED] Behalf Of Matt Munz Sent: Friday, February 28, 2003 8:54 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] stop using JDK 1.4 for development Bill, I thought JBoss was going to support 1.4. Is this not the case? - Matt -Original Message- From: Bill Burke [mailto:[EMAIL PROTECTED] Sent: Fri 2/28/2003 8:42 AM To: Jboss-Dev Cc: Subject: [JBoss-dev] stop using JDK 1.4 for development There have been a lot of build breakages lately because people are using JDK 1.4 features and they break in JDK 1.3 builds. WE STILL SUPPORT JDK 1.3. My suggestion? Stop developing JBOss with jdk 1.4 and develop with 1.3. Please stop the sloppiness. Bill --- 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 winmail.dat
Re: [JBoss-dev] stop using JDK 1.4 for development
I'd prefer to have a reliable way to report these problems, since I don't consider it realistic for me to develop on 1.3.1. How do you detect them? For the particular problem of nested exceptions, I think we should always use the jboss NestedThrowable stuff Jason wrote since it provides a much more reasonable stack trace. Dain and I made as much as we could find of the jca and jta frameworks use this with good results. How could we make this better known and popularize it? thanks david jencks On 2003.02.28 08:42 Bill Burke wrote: There have been a lot of build breakages lately because people are using JDK 1.4 features and they break in JDK 1.3 builds. WE STILL SUPPORT JDK 1.3. My suggestion? Stop developing JBOss with jdk 1.4 and develop with 1.3. Please stop the sloppiness. Bill --- 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] stop using JDK 1.4 for development
The problem really is with me - I fess up. Bill's mad because I broke the build twice this week by inadvertantly checking in code (throwing an exception that is the new overloaded version in 1.4) that only compiles on 1.4. Unfortunately, my whole work and home environment *DO* require 1.4 and only works under 1.4 - so I sometimes forget to re-set my path to JDK1.3 when I compile. So, it compiles fine under 1.4. I'm changing my jboss build environment to force my path and JDK to 1.3 before it runs. Maybe be can update the build.bat/.sh to automatically do this (or at least check the version before you compile) and that would fix this problem for everyone? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Jencks Sent: Friday, February 28, 2003 10:16 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] stop using JDK 1.4 for development I'd prefer to have a reliable way to report these problems, since I don't consider it realistic for me to develop on 1.3.1. How do you detect them? For the particular problem of nested exceptions, I think we should always use the jboss NestedThrowable stuff Jason wrote since it provides a much more reasonable stack trace. Dain and I made as much as we could find of the jca and jta frameworks use this with good results. How could we make this better known and popularize it? thanks david jencks On 2003.02.28 08:42 Bill Burke wrote: There have been a lot of build breakages lately because people are using JDK 1.4 features and they break in JDK 1.3 builds. WE STILL SUPPORT JDK 1.3. My suggestion? Stop developing JBOss with jdk 1.4 and develop with 1.3. Please stop the sloppiness. Bill --- 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] stop using JDK 1.4 for development
On 2003.02.28 10:23 Jeff Haynie wrote: The problem really is with me - I fess up. Bill's mad because I broke the build twice this week by inadvertantly checking in code (throwing an exception that is the new overloaded version in 1.4) that only compiles on 1.4. Unfortunately, my whole work and home environment *DO* require 1.4 and only works under 1.4 - so I sometimes forget to re-set my path to JDK1.3 when I compile. So, it compiles fine under 1.4. I'm changing my jboss build environment to force my path and JDK to 1.3 before it runs. Maybe be can update the build.bat/.sh to automatically do this (or at least check the version before you compile) and that would fix this problem for everyone? I don't think this is viable, since some features are simply going to be supported only on jdk 1.4. The primary example is working/reasonable transaction logging: I think non-blocking sockets versions of transport will be another example. I really think a reliable warning service is the way to go. I found Chris Kimpton's compilation reports so unreliable I stopped paying attention to them a long time ago. Are they useful to anyone? david -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Jencks Sent: Friday, February 28, 2003 10:16 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] stop using JDK 1.4 for development I'd prefer to have a reliable way to report these problems, since I don't consider it realistic for me to develop on 1.3.1. How do you detect them? For the particular problem of nested exceptions, I think we should always use the jboss NestedThrowable stuff Jason wrote since it provides a much more reasonable stack trace. Dain and I made as much as we could find of the jca and jta frameworks use this with good results. How could we make this better known and popularize it? thanks david jencks On 2003.02.28 08:42 Bill Burke wrote: There have been a lot of build breakages lately because people are using JDK 1.4 features and they break in JDK 1.3 builds. WE STILL SUPPORT JDK 1.3. My suggestion? Stop developing JBOss with jdk 1.4 and develop with 1.3. Please stop the sloppiness. Bill --- 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] stop using JDK 1.4 for development
We already have nested throwables (org.jboss.util.Nested*) that function in JDK 1.3 1.4, just use them. --jason On Friday, February 28, 2003, at 09:18 PM, Bill Burke wrote: We're not going to have .jpp or other ant switches just so that people can use nested exceptions -Original Message- From: Matt Munz [mailto:[EMAIL PROTECTED]On Behalf Of Matt Munz Sent: Friday, February 28, 2003 8:54 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] stop using JDK 1.4 for development Bill, I thought JBoss was going to support 1.4. Is this not the case? - Matt -Original Message- From: Bill Burke [mailto:[EMAIL PROTECTED] Sent: Fri 2/28/2003 8:42 AM To: Jboss-Dev Cc: Subject: [JBoss-dev] stop using JDK 1.4 for development There have been a lot of build breakages lately because people are using JDK 1.4 features and they break in JDK 1.3 builds. WE STILL SUPPORT JDK 1.3. My suggestion? Stop developing JBOss with jdk 1.4 and develop with 1.3. Please stop the sloppiness. Bill --- 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 winmail.dat>
RE: [JBoss-dev] stop using JDK 1.4 for development
David, This is probably none of my business, but... I'd prefer to have a reliable way to report these problems, since I don't consider it realistic for me to develop on 1.3.1. How do you detect them? Isn't this what integration builds and tests are for? If someone checks in code that does not compile and pass integration tests on all supported platforms, then it should probably be rolled back. How could we make this better known and popularize it? Perhaps a code conventions guide in addition to the code style guide? The Checkstyle tool (http://checkstyle.sourceforge.net) might also be used/modified to enforce this and other usage rules. - Matt -Original Message- From: David Jencks [mailto:[EMAIL PROTECTED] Sent: Fri 2/28/2003 10:16 AM To: [EMAIL PROTECTED] Cc: Subject: Re: [JBoss-dev] stop using JDK 1.4 for development I'd prefer to have a reliable way to report these problems, since I don't consider it realistic for me to develop on 1.3.1. How do you detect them? For the particular problem of nested exceptions, I think we should always use the jboss NestedThrowable stuff Jason wrote since it provides a much more reasonable stack trace. Dain and I made as much as we could find of the jca and jta frameworks use this with good results. How could we make this better known and popularize it? thanks david jencks On 2003.02.28 08:42 Bill Burke wrote: There have been a lot of build breakages lately because people are using JDK 1.4 features and they break in JDK 1.3 builds. WE STILL SUPPORT JDK 1.3. My suggestion? Stop developing JBOss with jdk 1.4 and develop with 1.3. Please stop the sloppiness. Bill --- 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 winmail.dat
Re: [JBoss-dev] stop using JDK 1.4 for development
This actually brings up another question. In using the JNP for JNDI detector (invoker stuff), it requires javax.net.ServerSocketFactory, which is in JDK 1.4 by default (and not in JDK 1.3). Therefore I compile and test using JDK 1.4 while doing my initial development locally. So when this is ready to checkin, will I have to then fix the build and CVS modules so that will know if using JDK 1.3, then go get the jnet.jar I need vs. if JDK 1.4 then don't have to do anything special. JBoss will have to move to JDK 1.4 sometime anyway if you want to keep up, so why not for JBoss 4? -Tom Jeff Haynie wrote: The problem really is with me - I fess up. Bill's mad because I broke the build twice this week by inadvertantly checking in code (throwing an exception that is the new overloaded version in 1.4) that only compiles on 1.4. Unfortunately, my whole work and home environment *DO* require 1.4 and only works under 1.4 - so I sometimes forget to re-set my path to JDK1.3 when I compile. So, it compiles fine under 1.4. I'm changing my jboss build environment to force my path and JDK to 1.3 before it runs. Maybe be can update the build.bat/.sh to automatically do this (or at least check the version before you compile) and that would fix this problem for everyone? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Jencks Sent: Friday, February 28, 2003 10:16 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] stop using JDK 1.4 for development I'd prefer to have a reliable way to report these problems, since I don't consider it realistic for me to develop on 1.3.1. How do you detect them? For the particular problem of nested exceptions, I think we should always use the jboss NestedThrowable stuff Jason wrote since it provides a much more reasonable stack trace. Dain and I made as much as we could find of the jca and jta frameworks use this with good results. How could we make this better known and popularize it? thanks david jencks On 2003.02.28 08:42 Bill Burke wrote: There have been a lot of build breakages lately because people are using JDK 1.4 features and they break in JDK 1.3 builds. WE STILL SUPPORT JDK 1.3. My suggestion? Stop developing JBOss with jdk 1.4 and develop with 1.3. Please stop the sloppiness. Bill --- 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] stop using JDK 1.4 for development
Any automated build and reporting system would be valuable... just depends on the implementation as to whether it is useful or not. --jason On Friday, February 28, 2003, at 10:36 PM, David Jencks wrote: On 2003.02.28 10:23 Jeff Haynie wrote: The problem really is with me - I fess up. Bill's mad because I broke the build twice this week by inadvertantly checking in code (throwing an exception that is the new overloaded version in 1.4) that only compiles on 1.4. Unfortunately, my whole work and home environment *DO* require 1.4 and only works under 1.4 - so I sometimes forget to re-set my path to JDK1.3 when I compile. So, it compiles fine under 1.4. I'm changing my jboss build environment to force my path and JDK to 1.3 before it runs. Maybe be can update the build.bat/.sh to automatically do this (or at least check the version before you compile) and that would fix this problem for everyone? I don't think this is viable, since some features are simply going to be supported only on jdk 1.4. The primary example is working/reasonable transaction logging: I think non-blocking sockets versions of transport will be another example. I really think a reliable warning service is the way to go. I found Chris Kimpton's compilation reports so unreliable I stopped paying attention to them a long time ago. Are they useful to anyone? david -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Jencks Sent: Friday, February 28, 2003 10:16 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] stop using JDK 1.4 for development I'd prefer to have a reliable way to report these problems, since I don't consider it realistic for me to develop on 1.3.1. How do you detect them? For the particular problem of nested exceptions, I think we should always use the jboss NestedThrowable stuff Jason wrote since it provides a much more reasonable stack trace. Dain and I made as much as we could find of the jca and jta frameworks use this with good results. How could we make this better known and popularize it? thanks david jencks On 2003.02.28 08:42 Bill Burke wrote: There have been a lot of build breakages lately because people are using JDK 1.4 features and they break in JDK 1.3 builds. WE STILL SUPPORT JDK 1.3. My suggestion? Stop developing JBOss with jdk 1.4 and develop with 1.3. Please stop the sloppiness. Bill --- 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] stop using JDK 1.4 for development
chris kimptons builds are perfect, but definately not useless. I'll be setting up a nightly build as soon as I get my new machine. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jason Dillon Sent: Friday, February 28, 2003 10:53 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] stop using JDK 1.4 for development Any automated build and reporting system would be valuable... just depends on the implementation as to whether it is useful or not. --jason On Friday, February 28, 2003, at 10:36 PM, David Jencks wrote: On 2003.02.28 10:23 Jeff Haynie wrote: The problem really is with me - I fess up. Bill's mad because I broke the build twice this week by inadvertantly checking in code (throwing an exception that is the new overloaded version in 1.4) that only compiles on 1.4. Unfortunately, my whole work and home environment *DO* require 1.4 and only works under 1.4 - so I sometimes forget to re-set my path to JDK1.3 when I compile. So, it compiles fine under 1.4. I'm changing my jboss build environment to force my path and JDK to 1.3 before it runs. Maybe be can update the build.bat/.sh to automatically do this (or at least check the version before you compile) and that would fix this problem for everyone? I don't think this is viable, since some features are simply going to be supported only on jdk 1.4. The primary example is working/reasonable transaction logging: I think non-blocking sockets versions of transport will be another example. I really think a reliable warning service is the way to go. I found Chris Kimpton's compilation reports so unreliable I stopped paying attention to them a long time ago. Are they useful to anyone? david -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Jencks Sent: Friday, February 28, 2003 10:16 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] stop using JDK 1.4 for development I'd prefer to have a reliable way to report these problems, since I don't consider it realistic for me to develop on 1.3.1. How do you detect them? For the particular problem of nested exceptions, I think we should always use the jboss NestedThrowable stuff Jason wrote since it provides a much more reasonable stack trace. Dain and I made as much as we could find of the jca and jta frameworks use this with good results. How could we make this better known and popularize it? thanks david jencks On 2003.02.28 08:42 Bill Burke wrote: There have been a lot of build breakages lately because people are using JDK 1.4 features and they break in JDK 1.3 builds. WE STILL SUPPORT JDK 1.3. My suggestion? Stop developing JBOss with jdk 1.4 and develop with 1.3. Please stop the sloppiness. Bill --- 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] stop using JDK 1.4 for development
I meant to say not perfect. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Bill Burke Sent: Friday, February 28, 2003 11:27 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] stop using JDK 1.4 for development chris kimptons builds are perfect, but definately not useless. I'll be setting up a nightly build as soon as I get my new machine. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jason Dillon Sent: Friday, February 28, 2003 10:53 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] stop using JDK 1.4 for development Any automated build and reporting system would be valuable... just depends on the implementation as to whether it is useful or not. --jason On Friday, February 28, 2003, at 10:36 PM, David Jencks wrote: On 2003.02.28 10:23 Jeff Haynie wrote: The problem really is with me - I fess up. Bill's mad because I broke the build twice this week by inadvertantly checking in code (throwing an exception that is the new overloaded version in 1.4) that only compiles on 1.4. Unfortunately, my whole work and home environment *DO* require 1.4 and only works under 1.4 - so I sometimes forget to re-set my path to JDK1.3 when I compile. So, it compiles fine under 1.4. I'm changing my jboss build environment to force my path and JDK to 1.3 before it runs. Maybe be can update the build.bat/.sh to automatically do this (or at least check the version before you compile) and that would fix this problem for everyone? I don't think this is viable, since some features are simply going to be supported only on jdk 1.4. The primary example is working/reasonable transaction logging: I think non-blocking sockets versions of transport will be another example. I really think a reliable warning service is the way to go. I found Chris Kimpton's compilation reports so unreliable I stopped paying attention to them a long time ago. Are they useful to anyone? david -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Jencks Sent: Friday, February 28, 2003 10:16 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] stop using JDK 1.4 for development I'd prefer to have a reliable way to report these problems, since I don't consider it realistic for me to develop on 1.3.1. How do you detect them? For the particular problem of nested exceptions, I think we should always use the jboss NestedThrowable stuff Jason wrote since it provides a much more reasonable stack trace. Dain and I made as much as we could find of the jca and jta frameworks use this with good results. How could we make this better known and popularize it? thanks david jencks On 2003.02.28 08:42 Bill Burke wrote: There have been a lot of build breakages lately because people are using JDK 1.4 features and they break in JDK 1.3 builds. WE STILL SUPPORT JDK 1.3. My suggestion? Stop developing JBOss with jdk 1.4 and develop with 1.3. Please stop the sloppiness. Bill --- 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
