db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David W. Van Couvering" <David.Vancouver...@Sun.COM>
Subject Re: Client SQLException change causing build failure
Date Sat, 28 Jan 2006 19:14:46 GMT
I just checked the test pages, and tests are running and (generally) 
passing with the JDK 1.5 builds done by DBTG.

I did a test build on JDK 1.4 and all is OK.  I did a test build on JDK 
1.6 and indeed the build fails, but my failures are different, and 
appear to be a poor configuration on my part (I have never tried this 
before), as I am getting syntax errors when the compiler hits generic types.

Rick -- you also mentioned that JDK 1.6 builds were breaking, and you 
were working on a fix.  Is this the same as what Andrew's seeing?  I 
don't want to step on your toes if you're already fixing this.

David


Andrew McIntyre wrote:
> Hi David,
> 
> I think that your changes that went in with revision 371561 are
> causing ClientPooledConnection40.java to fail to compile:
> 
> compile_jdbc4_target:
>      [echo]     [javac]
> C:\derby-trunk\java\client\org\apache\derby\client\ClientPooledConnection40.java:32:
> unreported exception java.sql.SQLException; must be caught or declared
> to be thrown
>      [echo]     [javac]         super(ds,logWriter,user,password);
>      [echo]     [javac]              ^
> 
> <snip other two errors>
> 
>      [echo]     [javac] 3 errors
>      [echo]
>      [echo] BUILD FAILED
> 
> Because ClientPooledConnection40 extends ClientPooledConnection, but
> the latter now throws SQLExceptions instead of SqlExceptions. Take a
> look if you have a moment.
> 
> Thanks,
> andrew

Mime
View raw message