ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 28681] - [PATCH] Xml output for the SQL task
Date Thu, 06 May 2004 18:10:53 GMT
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=28681>.
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=28681

[PATCH] Xml output for the SQL task





------- Additional Comments From jax@purematrix.com  2004-05-06 18:10 -------
Excuse me for interjecting a comment. As one of the other Sql task "activists"
here, I agree with Jose Alberto Fernandez. I would rather see a new task than
see task Sql have its code fancied up with features. At present, the
SQLExec.java code implementing critical functionality relevant to the core
mission of Ant is a readable piece of code. Core tasks should be allowed to
persevere in such a state to the greatest extent possible.

Better to create a new task and only use well-characterized project-wide
patterns to hook SQLExec.java if necessary to nest the new result set formatting
task. If it does not require hooks, then why not submit the formatter to
Ant-Contrib where it can comforatbly enter the tree in an underdesigned
first-cut state and evolve as one works out the requirements more fully?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message