db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.Narayanan (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-768) Build doesnt fail inspite of presence of a bug in JDBC4.0 specific classes and setting proceed=false
Date Sun, 12 Feb 2006 12:02:33 GMT
    [ http://issues.apache.org/jira/browse/DERBY-768?page=comments#action_12366101 ] 

V.Narayanan commented on DERBY-768:
-----------------------------------

Hi,
Derby-932 fixes this issue. When a bug is introduced in the JDBC4.0 classes the build breaks
when proceed=false.
Narayanan

> Build doesnt fail inspite of presence of a bug in JDBC4.0 specific classes  and setting
proceed=false
> -----------------------------------------------------------------------------------------------------
>
>          Key: DERBY-768
>          URL: http://issues.apache.org/jira/browse/DERBY-768
>      Project: Derby
>         Type: Bug
>   Components: Build tools
>     Reporter: V.Narayanan
>     Assignee: V.Narayanan
>  Attachments: build.diff
>
> The jdbc4 target does not echo anything about number of files compiled, as does the ordinary
compilation. Then, when a bug is inserted in a file (CallableStatement40.java), the build
proceeds in spite of setting proceed=false in ant.propeties. The build eventually reports
BUILD SUCCEEDED, although the JDBC4 build failed.
> ---------------------------------------- build log snippet:
> compile_jdbc4_target:
>      [exec] Result: 1
>      [echo]     [javac] /home/dw136774/derby/trunk/java/client/org/apache/derby/client/ClientPooledConnection40.java:26:
class, interface, or enum expected
>      [echo]     [javac] foobar public class ClientPooledConnection40 extends ClientPooledConnection
{
>      [echo]     [javac] ^
>      [echo]     [javac] 1 error
>      [echo] 
>      [echo] BUILD FAILED
>      [echo] /home/dw136774/derby/trunk/java/client/build.xml:67: Compile failed; see
the compiler error output for details.
>      [echo] 
>      [echo] Total time: 1 second
> build:
> build_base:
> compile:
> build:
> build:
> ckversioninfo:
> writeversioninfo:
> versioninfo:
> checklocaleinfo:
> localeinfo:
> buildsource:
> demo:
> compile:
> demo:
> testing:
> testing:
> init:
> compile:
> copyfiles:
> FTharness:
> copyfiles:
> testdata:
> copyfiles:
> compile:
> FTpolicy:
> util:
> checkjikessource:
> compilex_gump:
> compilex_nosource:
> compilex:
> FTOtestsubdir:
> compilet1:
> copyfiles:
> FTOtestsubdir:
> compilex:
> compilet2:
> compilet1:
> copyfiles:
> FTOtestsubdir:
> compilet3:
> compilet2:
> compilet1:
> copyfiles:
> FTOtestsubdir:
> compile:
> copyfiles:
> FTOtestsubdir:
> compile:
> copyfiles:
> FTOtestsubdir:
> compilet2:
> compilet1:
> copyfiles:
> FTOtestsubdir:
> copyfiles:
> FTOtestsubdir:
> compile:
> FTOtestsubdir:
> compilet2:
> compilet1:
> copyfiles:
> FTOtestsubdir:
> copyfiles:
> FTOtestsubdir:
> compile:
> copyfiles:
> FTOtestsubdir:
> compilet1:
> copyfiles:
> FTOtestsubdir:
> copyfiles:
> FTstress:
> copyfiles:
> FTmaster:
> copyfiles:
> suites:
> compile_jdbc4_target:
>      [echo] BUILD SUCCESSFUL
>      [echo] Total time: 1 second
> all:
> BUILD SUCCESSFUL
> Total time: 34 seconds

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message