On 11/13/05, robert burrell donkin <[EMAIL PROTECTED]> wrote: > On Sun, 2005-11-13 at 19:16 +0000, Stephen Colebourne wrote: > > Mario Ivankovits wrote: > > >> The jar was built with JDK1.4. Are targetting only JDK1.4? If you > > >> target 1.2/1.3, then it is possible that your jar won't work. I > > >> recommend compiling using the earliest JDK possible. > > > > > > Sure, but e.g. commons-net 1.4.0 was built with 1.4 too (+target 1.4), > > > and thus I cant use the 1.3 compiler as the build will fail if I do so. > > > > Sounds like a new [net] is needed pronto. > > +1 > > > > As far as I know the next NET version will be able to use target 1.3 > > > again, then I'll revert to use a java 1.3 compiler with maven too. > > > Anyway, VFS uses target=1.3 and I use the jdk 1.3 libraries during > > > development - so if your setup is correct (xml apis, java crypto, ...) > > > it should work. > > No. Not necessarily. See > > http://jroller.com/page/scolebourne?entry=compiling_for_older_jdks > > > > I think that the bootclasspath is what you need to solve the inability > > to use [net] from 1.3 issue too. > > +1 > > is this issue covered well enough in the release documentation?
See the "Check Class File Format" section in http://jakarta.apache.org/commons/releases/prepare.html Assuming all agree that compilation itself *must* be done on the lowest supported jdk, the text there should be updated to make that requirement explicit. I will update the docs if we can agree on a reasonable way to do this using maven, as well as ant. Phil > > - robert > > > --------------------------------------------------------------------- > 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]
