The jnet.jar is available and used in the build since it currently compiles with 1.3. If you are adding a new feature using javax.net.ServerSocketFactory then you may have to modify the corresponding build to include this jar to ensure that the code compiles with 1.3.
We have no plans on dropping support for 1.3.1 for the 4.0 release as there are too many users that have not moved to 1.4+. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Tom Elrod" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, February 28, 2003 7:51 AM Subject: 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 ------------------------------------------------------- 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
