cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Torsten Curdt <>
Subject Re: [Proposal] Splitting JDK dependent code [was: Re: Javac task design problems]
Date Tue, 25 Feb 2003 17:39:47 GMT

> If you want one base class for Java 1.2 and one derived class for Java 
> 1.4... Just check that Java 1.4 will work with that... How it will react 
> on non-abstract class (BaseEsqlConnection) which does not implement 
> interface (Connection) fully?
> Or you want to have one abstract (BaseAbstractEsqlConnection) and two 
> concrete classes (EsqlConnection12 and EsqlConnection14)?

Well, binary compatible or not we already have this warning message in 
our build:

"This build is targeted for use with JVM ${target.vm}"
"Using this build on a virtual machine other than the one"
"it is targeted for may result in runtime errors."


View raw message