[ http://issues.apache.org/jira/browse/DERBY-768?page=comments#action_12361813 ]
V.Narayanan commented on DERBY-768: ----------------------------------- Thank you for looking at this one Rick. The problem seems to be cygwin specific. Applying the same patch to my workspace in the solaris environment and introducing a bug in CallableStatement40 produces the following output. I observed from your ant output that you have actually set proceed =no. But it defaults to false. So the build has to fail. Which it does for me. The problem seems to be in the failonerror attribute. "By default the return code of a <exec> is ignored; when you set failonerror="true" then any return code signaling failure (OS specific) causes the build to fail. Alternatively, you can set resultproperty to the name of a property and have it assigned to the result code (barring immutability, of course)." quote unquote from http://ant.apache.org/manual/CoreTasks/exec.html . o/p in solaris environment for reference ----------------------------------------------------- ant -quiet all [echo] Ant environment: [echo] Base Directory: /space/Narayanan/derby_workspaces/derby3/trunk [echo] Build output: /space/Narayanan/derby_workspaces/derby3/trunk/classes [echo] Compiler: modern [echo] Sane = true [echo] Proceed = no [echo] Generating SanityState.java... [echo] Generating ij parser... [java] Warning: Lookahead adequacy checking not being performed since option LOOKAHEAD is more than 1. Set option FORCE_LA_CHECK to true to force checking. [echo] Generating mtGrammar parser... [echo] Generating SQL parser... [java] Warning: ParseException.java: File is obsolete. Please rename or delete this file so that a new one can be generated for you. [java] Warning: Token.java: File is obsolete. Please rename or delete this file so that a new one can be generated for you. [java] Warning: CharStream.java: File is obsolete. Please rename or delete this file so that a new one can be generated for you. [javac] 2 warnings [javac] 1 warning [javac] 1 warning [javac] 8 warnings [javac] 3 warnings [javac] 1 warning [javac] 77 warnings [exec] BUILD FAILED [exec] /space/Narayanan/derby_workspaces/derby3/trunk/java/client/build.xml:67: Compile failed; see the compiler error output for details. [exec] Total time: 2 seconds BUILD FAILED /space/Narayanan/derby_workspaces/derby3/trunk/build.xml:317: The following error occurred while executing this line: /space/Narayanan/derby_workspaces/derby3/trunk/build.xml:1376: exec returned: 1 Total time: 1 minute 21 seconds > 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
