You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "V.Narayanan (JIRA)" <de...@db.apache.org> on 2005/12/16 10:47:45 UTC
[jira] Created: (DERBY-768) Build doesnt fail inspite of presence of a bug in JDBC4.0 specific classes and setting proceed=false
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
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
[jira] Closed: (DERBY-768) Build doesnt fail inspite of presence of
a bug in JDBC4.0 specific classes and setting proceed=false
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-768?page=all ]
Andrew McIntyre closed DERBY-768:
---------------------------------
Fix Version: 10.2.0.0
Resolution: Fixed
Closing. Fixed with DERBY-932.
> 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
> Fix For: 10.2.0.0
> 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
[jira] Updated: (DERBY-768) Build doesnt fail inspite of presence of a bug in JDBC4.0 specific classes and setting proceed=false
Posted by "V.Narayanan (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Assigned: (DERBY-768) Build doesnt fail inspite of presence of a bug in JDBC4.0 specific classes and setting proceed=false
Posted by "V.Narayanan (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-768?page=all ]
V.Narayanan reassigned DERBY-768:
---------------------------------
Assign To: V.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
>
> 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
Re: [jira] Commented: (DERBY-768) Build doesnt fail inspite of
presence of a bug in JDBC4.0 specific classes and setting proceed=false
Posted by Rick Hillegas <Ri...@Sun.COM>.
Hi Narayanan,
Thanks for the clarification. The -quiet flag throttles various
diagnostic output but isn't supposed to swallow compiler errors. If I
seed an engine class with junk and then compile using the -quiet flag, I
still see the compiler errors for the engine class. I think that the
jdbc4 compilation should behave the same way.
Regards,
-Rick
V Narayanan - Sun Microsystems - Bangalore India wrote:
> 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
>>
>>
>>
>
Re: [jira] Commented: (DERBY-768) Build doesnt fail inspite of
presence of a bug in JDBC4.0 specific classes and setting proceed=false
Posted by V Narayanan - Sun Microsystems - Bangalore India <V....@Sun.COM>.
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
>
>
[jira] Commented: (DERBY-768) Build doesnt fail inspite of presence of a bug in JDBC4.0 specific classes and setting proceed=false
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ 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
--
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
[jira] Commented: (DERBY-768) Build doesnt fail inspite of presence of a bug in JDBC4.0 specific classes and setting proceed=false
Posted by "V.Narayanan (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Commented: (DERBY-768) Build doesnt fail inspite of presence of a bug in JDBC4.0 specific classes and setting proceed=false
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-768?page=comments#action_12361779 ]
Rick Hillegas commented on DERBY-768:
-------------------------------------
I'm afraid this patch does not seem to fix the problem, at least when run on my environment: cygwin under XP. I ran the following experiments:
A) I inserted garbage into an engine class (AggregateNode.java) and then ran "ant -quiet all".
B) Then I removed those edits, did an "ant -quiet clean", inserted garbage into a JDBC 4.0 class (CallableStatement40.java), and ran "ant -quiet all"
In experiment (A), I saw compiler errors and the build terminated after stumbling on the garbage.
In experiment (B), however, I did not see any compiler errors (just an indication that some error had occurred). In addition, the compilation continued after stumbling on the garbage. Here is the output from experiment (B):
[echo] Ant environment:
[echo] Base Directory: C:\cygwin\home\rh161140\derby\mainline\trunk
[echo] Build output: C:\cygwin\home\rh161140\derby\mainline\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 gene
rated for you.
[javac] 2 warnings
[javac] 1 warning
[javac] 8 warnings
[javac] 3 warnings
[javac] 1 warning
[javac] 77 warnings
[exec] BUILD FAILED
[exec] C:\cygwin\home\rh161140\derby\mainline\trunk\java\client\build.xml:67: Compile failed; see the compiler erro
r output for details.
[exec] Total time: 1 second
[javac] 3 warnings
[javac] 3 warnings
[javac] 3 warnings
BUILD SUCCESSFUL
Total time: 1 minute 17 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
[jira] Commented: (DERBY-768) Build doesnt fail inspite of presence
of a bug in JDBC4.0 specific classes and setting proceed=false
Posted by "V.Narayanan (JIRA)" <de...@db.apache.org>.
[ 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