youys
/
ant
Not watched
1
0
Fork 1
Code
Releases 0 Wiki Activity
Issues 0 Pull Requests 0 Datasets Model Cloudbrain
Browse Source

Mailinglists have moved 

git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@274042 13f79535-47bb-0310-9956-ffa450edef68
master
Stefan Bodewig 22 years ago
parent
1dc8a07905
commit
1c0b70100b
6 changed files with 13 additions and 41 deletions
Split View
Diff Options
Show Stats Download Patch File Download Diff File
  1. +1
    -1
      docs/ant_in_anger.html
  2. +4
    -4
      docs/ant_task_guidelines.html
  3. +0
    -10
      docs/mail.html
  4. +4
    -8
      docs/problems.html
  5. +0
    -10
      xdocs/mail.xml
  6. +4
    -8
      xdocs/problems.xml

+ 1
- 1
docs/ant_in_anger.html View File

@@ -626,7 +626,7 @@ with all the other crises.
<p>

You should also get on the <a href =
"mailto:ant-dev-subscribe@jakarta.apache.org" > ant-dev mailing list
"mailto:dev-subscribe@ant.apache.org" > dev mailing list
</a>, 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


+ 4
- 4
docs/ant_task_guidelines.html View File

@@ -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.

<p>
@@ -351,7 +351,7 @@ line of code.
The process for submitting an Ant task is documented on the
<a href="http://jakarta.apache.org/site/guidelines.html">
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
any debate about your own submission.
<p>
@@ -413,7 +413,7 @@ cases, while documentation helps sell the reason for a task.
<li>Documentation page extended as appropriate.
<li>Example task declarations in the documentation tested.
<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.
<li>Message body contains a rationale for the patch.
<li>Message attachment contains the patch file(s).
@@ -436,7 +436,7 @@ subject.
tasks
<li>patch files include a patch to coretasklist.html or
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 attachments contain the required files -source, documentation,
test and patches zipped up to escape the HTML filter.


+ 0
- 10
docs/mail.html View File

@@ -221,14 +221,9 @@
</table>
<p>
<b>Medium Traffic</b>
<!--
<a href="mailto:user-subscribe@ant.apache.org">Subscribe</a>
<a href="mailto:user-unsubscribe@ant.apache.org">Unsubscribe</a>
<a href="http://archives.apache.org/eyebrowse/SummarizeList?listName=ant-user@jakarta.apache.org">Archive</a>
-->
<a href="mailto:ant-user-subscribe@jakarta.apache.org">Subscribe</a>
<a href="mailto:ant-user-unsubscribe@jakarta.apache.org">Unsubscribe</a>
<a href="http://archives.apache.org/eyebrowse/SummarizeList?listName=ant-user@jakarta.apache.org">Archive</a>
</p>
<p>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 @@
</table>
<p>
<b>High Traffic</b>
<!--
<a href="mailto:dev-subscribe@ant.apache.org">Subscribe</a>
<a href="mailto:dev-unsubscribe@ant.apache.org">Unsubscribe</a>
<a href="http://archives.apache.org/eyebrowse/SummarizeList?listName=ant-dev@jakarta.apache.org">Archive</a>
-->
<a href="mailto:ant-dev-subscribe@jakarta.apache.org">Subscribe</a>
<a href="mailto:ant-dev-unsubscribe@jakarta.apache.org">Unsubscribe</a>
<a href="http://archives.apache.org/eyebrowse/SummarizeList?listName=ant-dev@jakarta.apache.org">Archive</a>
</p>
<p>This is the list where participating developers of the Ant
build tool meet and discuss issues, code changes/additions,


+ 4
- 8
docs/problems.html View File

@@ -408,8 +408,7 @@ D:\src\java\Unset.java<br />
<p>
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 <code>user</code> mailing list-->
an email to the <code>ant-user</code> mailing list
an email to the <code>user</code> 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<br />
<a href="http://ant.apache.org/srcdownload.cgi">
source distributions</a>. If you
are going to tackle the problem at this level, you may want to
<!-- discuss some details first on the <code>dev</code>-->
discuss some details first on the <code>ant-dev</code>
discuss some details first on the <code>dev</code>
mailing list. Once you have a fix for the problem, you may submit
the fix as a <i>patch</i> to either the
<!-- <code>dev</code> mailing-->
<code>ant-dev</code> mailing
<code>dev</code> 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.
</p>
<p>
If you have a patch to submit and are sending it to the
<!-- <code>dev</code> mailing list,-->
<code>ant-dev</code> mailing list,
<code>dev</code> mailing list,
prefix "[PATCH]"
to your message subject. Please include any relevant bug numbers.
Patch files should be created with the <code>-u</code>


+ 0
- 10
xdocs/mail.xml View File

@@ -26,14 +26,9 @@
<subsection name="User List">
<p>
<b>Medium Traffic</b>
<!--
<a href="mailto:user-subscribe@ant.apache.org">Subscribe</a>
<a href="mailto:user-unsubscribe@ant.apache.org">Unsubscribe</a>
<a href="http://archives.apache.org/eyebrowse/SummarizeList?listName=ant-user@jakarta.apache.org">Archive</a>
-->
<a href="mailto:ant-user-subscribe@jakarta.apache.org">Subscribe</a>
<a href="mailto:ant-user-unsubscribe@jakarta.apache.org">Unsubscribe</a>
<a href="http://archives.apache.org/eyebrowse/SummarizeList?listName=ant-user@jakarta.apache.org">Archive</a>
</p>

<p>This list is for developers that are using Ant in their own
@@ -44,14 +39,9 @@
<subsection name="Developer List">
<p>
<b>High Traffic</b>
<!--
<a href="mailto:dev-subscribe@ant.apache.org">Subscribe</a>
<a href="mailto:dev-unsubscribe@ant.apache.org">Unsubscribe</a>
<a href="http://archives.apache.org/eyebrowse/SummarizeList?listName=ant-dev@jakarta.apache.org">Archive</a>
-->
<a href="mailto:ant-dev-subscribe@jakarta.apache.org">Subscribe</a>
<a href="mailto:ant-dev-unsubscribe@jakarta.apache.org">Unsubscribe</a>
<a href="http://archives.apache.org/eyebrowse/SummarizeList?listName=ant-dev@jakarta.apache.org">Archive</a>
</p>

<p>This is the list where participating developers of the Ant


+ 4
- 8
xdocs/problems.xml View File

@@ -177,8 +177,7 @@ D:\src\java\Unset.java<br></br>
<p>
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 <code>user</code> mailing list-->
an email to the <code>ant-user</code> mailing list
an email to the <code>user</code> 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<br></br>
<a href="http://ant.apache.org/srcdownload.cgi">
source distributions</a>. If you
are going to tackle the problem at this level, you may want to
<!-- discuss some details first on the <code>dev</code>-->
discuss some details first on the <code>ant-dev</code>
discuss some details first on the <code>dev</code>
mailing list. Once you have a fix for the problem, you may submit
the fix as a <i>patch</i> to either the
<!-- <code>dev</code> mailing-->
<code>ant-dev</code> mailing
<code>dev</code> 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.
</p>
<p>
If you have a patch to submit and are sending it to the
<!-- <code>dev</code> mailing list,-->
<code>ant-dev</code> mailing list,
<code>dev</code> mailing list,
prefix &quot;[PATCH]&quot;
to your message subject. Please include any relevant bug numbers.
Patch files should be created with the <code>-u</code>


Write Preview
Loading…
Cancel
Save