|
List Info
Thread: DO NOT REPLY New: - Add an errorproperty parameter to task, like the junit task's
|
|
| DO NOT REPLY New: - Add an
errorproperty parameter to <sql>
task, like the junit task's |

|
2006-02-28 12:44:32 |
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38
807>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38807
a>
Summary: Add an errorproperty parameter to
<sql> task, like the
junit task's
Product: Ant
Version: 1.6.5
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: enhancement
Priority: P3
Component: Core tasks
AssignedTo: dev ant.apache.org
ReportedBy: ats37 hotmail.com
I'm using the <sql> task with a fileset to read in a
whole bunch of stored proc
definitions into our unit test database prior to running the
tests. Although I
could use onerror="abort" (or stop) to make the
build fail if there are any
problems, this only reports the first file. What I'd find
more useful would be
to use onerror="continue" in conjunction with an
errorproperty attribute (like
the junit task has) so that all the errors appear in my log
file, but a property
gets set which I can check later in the build (and either
fail or skip the unit
tests).
And, while I'm wishing, a warningproperty property which
gets set if the
conn.getWarnings() call returns anything in execSQL() might
also be useful.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=ema
il
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the
assignee.
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribe ant.apache.org
For additional commands, e-mail: dev-help ant.apache.org
|
|
[1]
|
|
|
about | contact Other archives ( Real Estate discussion Medical topics )
|