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
