You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Dyre Tjeldvoll <Dy...@Sun.COM> on 2008/05/26 23:10:16 UTC

Build failure on Windows beginning in rev 658805

I'm seeing a build failure in 
D:\derby-safe\java\demo\vtis\java\org\apache\derbyDemo\vtis\core\Str
ingColumnVTI.java

when I compile on Windows, (but not on Solaris). I'm guessing that I 
somehow compile the vti classes against a different (newer?) version of 
the Blob/Clob interface... any thoughts about how that could happen?


vti-demo:

compile-vtidemo:

[...]

D:\derby-safe\java\demo\vtis\java\org\apache\derbyDemo\vtis\core\Str
ingColumnVTI.java:70: 
org.apache.derbyDemo.vtis.core.StringColumnVTI.SimpleBlob
is not abstract and does not override abstract method 
getBinaryStream(long,long)
  in java.sql.Blob
     [javac]     public  static  final   class   SimpleBlob      implements
Blob
     [javac]                             ^
     [javac] 
D:\derby-safe\java\demo\vtis\java\org\apache\derbyDemo\vtis\core\Str
ingColumnVTI.java:148: 
org.apache.derbyDemo.vtis.core.StringColumnVTI.SimpleClob
  is not abstract and does not override abstract method 
getCharacterStream(long,l
ong) in java.sql.Clob
     [javac]     public  static  final   class   SimpleClob      implements
Clob
     [javac]                             ^
     [javac] 
D:\derby-safe\java\demo\vtis\java\org\apache\derbyDemo\vtis\core\Xml
VTI.java:39: org.apache.derbyDemo.vtis.core.XmlVTI is not abstract and 
does not
override abstract method updateNClob(java.lang.String,java.io.Reader) in 
java.sq
l.ResultSet
     [javac] public  class   XmlVTI  extends StringColumnVTI
     [javac]         ^
     [javac] 
D:\derby-safe\java\demo\vtis\java\org\apache\derbyDemo\vtis\example\
LineListVTI.java:37: org.apache.derbyDemo.vtis.example.LineListVTI is 
not abstra
ct and does not override abstract method 
updateNClob(java.lang.String,java.io.Re
ader) in java.sql.ResultSet
     [javac] public    class   LineListVTI  extends FlatFileVTI
     [javac]           ^
     [javac] 
D:\derby-safe\java\demo\vtis\java\org\apache\derbyDemo\vtis\example\
PropertyFileVTI.java:35: 
org.apache.derbyDemo.vtis.example.PropertyFileVTI is no
t abstract and does not override abstract method 
updateNClob(java.lang.String,ja
va.io.Reader) in java.sql.ResultSet
     [javac] public    class   PropertyFileVTI  extends FlatFileVTI
     [javac]           ^
     [javac] 
D:\derby-safe\java\demo\vtis\java\org\apache\derbyDemo\vtis\example\
SubversionLogVTI.java:35: 
org.apache.derbyDemo.vtis.example.SubversionLogVTI is
not abstract and does not override abstract method 
updateNClob(java.lang.String,
java.io.Reader) in java.sql.ResultSet
     [javac] public    class   SubversionLogVTI  extends FlatFileVTI
     [javac]           ^
     [javac] Note: Some input files use unchecked or unsafe operations.
     [javac] Note: Recompile with -Xlint:unchecked for details.
     [javac] 6 errors
     [javac] 4 warnings

BUILD FAILED
D:\derby-safe\build.xml:448: The following error occurred while 
executing this l
ine:
D:\derby-safe\java\demo\build.xml:143: Compile failed; see the compiler 
error ou
tput for details.

Total time: 56 seconds


Dyre

Re: Build failure on Windows beginning in rev 658805

Posted by Dyre Tjeldvoll <Dy...@Sun.COM>.
Dyre Tjeldvoll wrote:
> I'm seeing a build failure in 
> D:\derby-safe\java\demo\vtis\java\org\apache\derbyDemo\vtis\core\Str
> ingColumnVTI.java
> 
> when I compile on Windows, (but not on Solaris). I'm guessing that I 
> somehow compile the vti classes against a different (newer?) version of 
> the Blob/Clob interface... any thoughts about how that could happen?

Indeed, I had pointed j15lib to java6/jre/lib, so when compiling the vti 
code which is at source level 1.5 I got the jdbc4 Blob/Clob interfaces.

Downloading jdk 1.5 and making j15lib point to it did the trick... (even 
if I did get an EOL warning when downloading Java 1.5... :)

Dyre