@@ -335,7 +335,7 @@ We've all done it: written and submitted a task only to discover it
was already implemented in a small corner of another task, or it has
was already implemented in a small corner of another task, or it has
been submitted by someone else and not committed. You can avoid this
been submitted by someone else and not committed. You can avoid this
by being aware of what is in the latest CVS tree -keep getting the daily
by being aware of what is in the latest CVS tree -keep getting the daily
source updates, look at manual changes and subscribe to the ant- dev
source updates, look at manual changes and subscribe to the dev
mailing list.
mailing list.
<p>
<p>
@@ -351,7 +351,7 @@ line of code.
The process for submitting an Ant task is documented on the
The process for submitting an Ant task is documented on the
<a href="http://jakarta.apache.org/site/guidelines.html">
<a href="http://jakarta.apache.org/site/guidelines.html">
jakarta web site</a>.
jakarta web site</a>.
The basic mechanism is to mail it to the ant- dev mailing list.
The basic mechanism is to mail it to the dev mailing list.
It helps to be on this list, as you will see other submissions, and
It helps to be on this list, as you will see other submissions, and
any debate about your own submission.
any debate about your own submission.
<p>
<p>
@@ -413,7 +413,7 @@ cases, while documentation helps sell the reason for a task.
<li>Documentation page extended as appropriate.
<li>Documentation page extended as appropriate.
<li>Example task declarations in the documentation tested.
<li>Example task declarations in the documentation tested.
<li>Diff files generated using cvs diff -u
<li>Diff files generated using cvs diff -u
<li>Message to ant- dev contains [PATCH], task name and patch reason in
<li>Message to dev contains [PATCH], task name and patch reason in
subject.
subject.
<li>Message body contains a rationale for the patch.
<li>Message body contains a rationale for the patch.
<li>Message attachment contains the patch file(s).
<li>Message attachment contains the patch file(s).
@@ -436,7 +436,7 @@ subject.
tasks
tasks
<li>patch files include a patch to coretasklist.html or
<li>patch files include a patch to coretasklist.html or
optionaltasklist.html to link to the new task page
optionaltasklist.html to link to the new task page
<li>Message to ant- dev contains [SUBMIT] and task name in subject
<li>Message to dev contains [SUBMIT] and task name in subject
<li>Message body contains a rationale for the task
<li>Message body contains a rationale for the task
<li>Message attachments contain the required files -source, documentation,
<li>Message attachments contain the required files -source, documentation,
test and patches zipped up to escape the HTML filter.
test and patches zipped up to escape the HTML filter.