On Tue, 27 Sep 2005, Henning P. Schmiedehausen wrote: > Daniel Rall <[EMAIL PROTECTED]> writes: > > >I'm okay with this, though a little iffy about the build succeeding and > >producing different results depending upon what's in your classpath. > >Perhaps the "release build" could be more stringent, and actually fail in > >the case where it might otherwise just not build some of the classes. > > I think, putting out a warning message should be enough. We could add > a property to the build.xml file which forces the build to fail on > missing classes though. This is only a problem for JDK's < 1.4 which > are quite antique these days, aren't they?
I didn't realize that that was the case for all of the J2EE stuff, but now that'cha mention it, sure sounds right (JDBC, and formerly, Servlets). Given that what you say about JDK versions is true for the people doing the build (though not necessarilly at runtime), I'm okay with the warning. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
