For example, one class in our project implements java.sql.Connection. A method was added to this interface in Java 1.4 (or 5.0?) and so compiling this class with -source 1.3 and -target 1.3 gives the following error:
D:\dev\workspace\promo-head\server\src\main\java\promo\util\xsql\XConnection.java:[19,7] promo.util.xsql.XConnection is not abstract and does not override abstract method prepareStatement(java.lang.String,java.lang.String[]) in java.sql.Connection There are similar errors, all related to the java.sql and javax.sql interfaces. I've read that it's a question of changing the boot classpath, but I could be mistaken. Thanks, GB ----- Original Message ---- From: Kaare Nilsen <[EMAIL PROTECTED]> To: Maven Users List <users@maven.apache.org> Sent: Wednesday, June 28, 2006 3:11:33 PM Subject: Re: AspectJ compiler with Java 1.3 On 28/06/06, Guillaume Bilodeau <[EMAIL PROTECTED]> wrote: > Hi all, > > I'm asking for your help once again. Our projects are currently compiled > using Java 1.3 through a Maven 2.0.4 build. We want to add some aspects > (through the new Spring 2.0 tags) and we need to switch to the AspectJ > compiler, while still using the Java 1.3 classes as a reference (to avoid > using APIs introduced in 1.4+). I've read the plugin documentation and it > seems like the only thing we can do is to use the source and target > configuration options, which is not sufficient. Why is that ? When setting the source and the target to 1.3 or the complianceLevel option to 1.3 (shorthand which sets -source to 1.3 and -target 1.1). This should do the trick, and if it does not, it is a bug. Could you then please send me a testproject that will trigger it ? > Did anyone do anything similar? > > Thanks, > GB
