Hi Rick,
I am sending this mail on the list because JIRA is down.
I observe this problem when I run ant with the "-quiet" flag. But when I
run it without the -quiet flag I observe the following.
compile_jdbc4_target:
[exec] Buildfile:
/space/Narayanan/derby_workspaces/derby3/trunk/java/client/build.xml
[exec] compile_jdbc4:
[exec] [javac] Compiling 8 source files to
/space/Narayanan/derby_workspaces/derby3/trunk/classes
[exec] [javac]
/space/Narayanan/derby_workspaces/derby3/trunk/java/client/org/apache/derby/client/am/CallableStatement40.java:32:
class, interface, or enum expected
[exec] [javac] foo public class CallableStatement40 extends
org.apache.derby.client.am.CallableStatement {
[exec] [javac] ^
[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 36 seconds
Rick Hillegas (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-768?page=comments#action_12361910 ]
Rick Hillegas commented on DERBY-768:
-------------------------------------
Hi Narayanan. Thanks for the clarification. From the output you attached, it
appears that in your environment, the build does stop after stumbling on errors
in jdbc4 classes. However, I don't see any compiler errors. All I see is a
cryptic line saying that some error occurred.
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
