commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Cohen <>
Subject Re: [net] JDK 1.1 question
Date Fri, 23 Jan 2004 02:04:16 GMT
On Thursday 22 January 2004 6:02 am, Steve Cohen wrote:
> On Thursday 22 January 2004 12:04 am, Steve Cohen wrote:
> > I have built a candidate release for 1.1.1.
> >
> > Testing it is has proven a bit problematical.  I found an old Blackdown
> > port of java 1.1.8 for Linux.  I don't believe Sun ever released a port
> > of Java 1.1 for Linux.  Whether this has ever been tested on RedHat 9.0
> > which it predates by three years, is dubious.  In any case, the behavior
> > I notice is that a sample test application attempts to connect() to an
> > ftp server. The call to connect() takes about 15 minutes to return, and
> > when it returns the connection is no longer valid.  Obviously there is
> > some sort of threading mismatch going on.
> >
> > So, the heck with that.  Let me try to install jdk118 for Windows.
> >
> > Now the programs experience no delays but throw the following exception:
> >
> > java.lang.NoClassDefFoundError: org/apache/oro/text/regex/Perl5Compiler
> >
> > Now I've looked up and down and there's no way oro-2.0.7.jar is not on
> > the classpath, and furthermore, it does contain
> > org/apache/oro/text/regex/Perl5Compiler
> >
> > I believe I've seen cases where these errors are thrown if there's
> > something in the jar class that cannot be resolved at runtime, even if
> > the class itself can be so resolved.
> >
> > Daniel, do you remember anything about anything in 2.0.7 that is not 1.1
> > compatible?  If that is so, it may be that all our 1.1 efforts for net
> > are for naught.
> Duh, of course there is a dependency.  I was too tired to see it last
> night. jakarta-oro-2.0.7's perl5 compiler uses HashMaps.  Is there perhaps
> an earlier version of the the oro package we could roll back to for 1.1
> compatibility that does not do this?

Looking into this further, it seems that jakarta-oro-2.0.1 is the most recent 
oro version that is executable under JDK-1.1 JVMs (actually, this applies 
only to Perl5Compiler, which seems to be the only jakarta-oro class that is 
both used by commons-net and incompatible with jdk 1.1).  I haven't fully 
analyzed jakarta-oro, only those classes used by net.

Question - primarily for Daniel:  Do you think it makes sense to dial back to 
using jakarta-oro-2.0.1 in commons-net.1.1.1 to preserve JDK 1.1. 
compatibility?  What features/bug fixes would be lost?  Unless we either do 
this or rewrite, we don't have a version that works under 1.1.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message