Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1551327254.1134726766464.JavaMail.jira@ajax.apache.org>
Date: Fri, 16 Dec 2005 10:52:46 +0100 (CET)
From: "V.Narayanan (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-768) Build doesnt fail inspite of presence of
 a bug in JDBC4.0 specific classes  and setting proceed=false
In-Reply-To: <88594995.1134726465706.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-768?page=all ]

V.Narayanan updated DERBY-768:
------------------------------

    Attachment: build.diff

1) JDBC4.0 compilation target does not echo anything about the number of
files printed
2) Upon inserting a bug and setting proceed=false the compilation
proceeds instead of failing

I have fixed this in addition to a small change documented below

a) Removing the -quiet option
b) Setting failonerror depending on the value of the proceed variable
c) Removing the echo task since if the exec task fails we would want 	
    the user to know the reason for failure which otherwise wouldnt be
   printed if echo occurred after the exec task
d) I am also removing the part of the build which checks os and sets
executable to ant or ant.bat and am instead using vmlauncher attribute
of the exec task and am setting it to false.

thanx,
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