diff --git a/docs/ant_in_anger.html b/docs/ant_in_anger.html index bd7339846..bbd1425b3 100644 --- a/docs/ant_in_anger.html +++ b/docs/ant_in_anger.html @@ -626,7 +626,7 @@ with all the other crises.

You should also get on the ant-dev mailing list +"mailto:dev-subscribe@ant.apache.org" > dev mailing list , as it is where the other developers post their work, problems and experience. The volume can be quite high: 40+ messages a day, so consider routing it to an email address you don't use for much else. And diff --git a/docs/ant_task_guidelines.html b/docs/ant_task_guidelines.html index 4e2292539..50cb12918 100644 --- a/docs/ant_task_guidelines.html +++ b/docs/ant_task_guidelines.html @@ -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 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 -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.

@@ -351,7 +351,7 @@ line of code. The process for submitting an Ant task is documented on the jakarta web site. -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 any debate about your own submission.

@@ -413,7 +413,7 @@ cases, while documentation helps sell the reason for a task.

  • Documentation page extended as appropriate.
  • Example task declarations in the documentation tested.
  • Diff files generated using cvs diff -u -
  • Message to ant-dev contains [PATCH], task name and patch reason in +
  • Message to dev contains [PATCH], task name and patch reason in subject.
  • Message body contains a rationale for the patch.
  • Message attachment contains the patch file(s). @@ -436,7 +436,7 @@ subject. tasks
  • patch files include a patch to coretasklist.html or optionaltasklist.html to link to the new task page -
  • Message to ant-dev contains [SUBMIT] and task name in subject +
  • Message to dev contains [SUBMIT] and task name in subject
  • Message body contains a rationale for the task
  • Message attachments contain the required files -source, documentation, test and patches zipped up to escape the HTML filter. diff --git a/docs/mail.html b/docs/mail.html index 3263d7fd5..c7d225ea8 100644 --- a/docs/mail.html +++ b/docs/mail.html @@ -221,14 +221,9 @@

    Medium Traffic - - Subscribe - Unsubscribe - Archive

    This list is for developers that are using Ant in their own projects to ask questions, share knowledge, and discuss issues @@ -244,14 +239,9 @@

    High Traffic - - Subscribe - Unsubscribe - Archive

    This is the list where participating developers of the Ant build tool meet and discuss issues, code changes/additions, diff --git a/docs/problems.html b/docs/problems.html index abafeba03..2b6e5b7b8 100644 --- a/docs/problems.html +++ b/docs/problems.html @@ -408,8 +408,7 @@ D:\src\java\Unset.java

    By this time, you may have decided that there is an unreported bug in Ant. You have a few choices at this point. You can send - - an email to the ant-user mailing list + an email to the user mailing list to see if others have encountered your issue and find out how they may have worked around it. If after some discussion, you feel it @@ -482,20 +481,17 @@ D:\src\java\Unset.java
    source distributions. If you are going to tackle the problem at this level, you may want to - - discuss some details first on the ant-dev + discuss some details first on the dev mailing list. Once you have a fix for the problem, you may submit the fix as a patch to either the - - ant-dev mailing + dev mailing list, or enter the bug database as described above and attach the patch to the bug report. Using the bug database has the advantage of being able to track the progress of your patch.

    If you have a patch to submit and are sending it to the - - ant-dev mailing list, + dev mailing list, prefix "[PATCH]" to your message subject. Please include any relevant bug numbers. Patch files should be created with the -u diff --git a/xdocs/mail.xml b/xdocs/mail.xml index 900daa6df..246fda964 100644 --- a/xdocs/mail.xml +++ b/xdocs/mail.xml @@ -26,14 +26,9 @@

    Medium Traffic - - Subscribe - Unsubscribe - Archive

    This list is for developers that are using Ant in their own @@ -44,14 +39,9 @@

    High Traffic - - Subscribe - Unsubscribe - Archive

    This is the list where participating developers of the Ant diff --git a/xdocs/problems.xml b/xdocs/problems.xml index d964794d0..40e580f84 100644 --- a/xdocs/problems.xml +++ b/xdocs/problems.xml @@ -177,8 +177,7 @@ D:\src\java\Unset.java

    By this time, you may have decided that there is an unreported bug in Ant. You have a few choices at this point. You can send - - an email to the ant-user mailing list + an email to the user mailing list to see if others have encountered your issue and find out how they may have worked around it. If after some discussion, you feel it @@ -239,20 +238,17 @@ D:\src\java\Unset.java

    source distributions. If you are going to tackle the problem at this level, you may want to - - discuss some details first on the ant-dev + discuss some details first on the dev mailing list. Once you have a fix for the problem, you may submit the fix as a patch to either the - - ant-dev mailing + dev mailing list, or enter the bug database as described above and attach the patch to the bug report. Using the bug database has the advantage of being able to track the progress of your patch.

    If you have a patch to submit and are sending it to the - - ant-dev mailing list, + dev mailing list, prefix "[PATCH]" to your message subject. Please include any relevant bug numbers. Patch files should be created with the -u