db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Hillegas <rick.hille...@oracle.com>
Subject Re: compile classpath for org.apache.derbyTesting.junit, was: Fwd: Build Report - tinderbox_trunk16 1197569 build failed - Sun Database Engineering [Auto-generated mail]
Date Mon, 07 Nov 2011 13:35:02 GMT
Any opinions on this one? The org.apache.derbyTesting.junit package 
contains JUnit test infrastructure which we expect to run on small 
platforms. Seems to me that we should be compiling this code against the 
small device classpath.


On 11/4/11 7:46 AM, Rick Hillegas wrote:
> The reason that my build environment did not catch this problem is 
> that the compile classpath for the org.apache.derbyTesting.junit 
> package is java14compile.classpath, which in my environment is a more 
> advanced jdk. Shouldn't the compile classpath of 
> org.apache.derbyTesting.junit be compile.classpath, the least capable 
> classpath we have, the one which checks that code will run on CDC/FP 
> 1.1? If we think that is so, I will open a JIRA to make this change. 
> It will involve fixing some classes in org.apache.derbyTesting.junit 
> which use apis which were introduced in jdk 1.4 but are not present in 
> CDC/FP 1.1.
> Thanks,
> -Rick

View raw message