From db1b34f91fbc80e44eed7ea2a0c2e14d3299fdb5 Mon Sep 17 00:00:00 2001 From: Stefan Bodewig Date: Mon, 4 Dec 2006 04:58:35 +0000 Subject: [PATCH] linefeeds git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@482074 13f79535-47bb-0310-9956-ffa450edef68 --- docs/external.html | 57 ++++++ xdocs/antlibs/svn/index.xml | 2 +- xdocs/bindownload.xml | 2 +- xdocs/bugs.xml | 342 ++++++++++++++++++------------------ xdocs/contributors.xml | 2 +- xdocs/faq.xml | 2 +- xdocs/mail.xml | 2 +- xdocs/projects.xml | 2 +- xdocs/srcdownload.xml | 2 +- xdocs/stylesheets/site.vsl | 2 +- xdocs/svn.xml | 2 +- 11 files changed, 237 insertions(+), 180 deletions(-) diff --git a/docs/external.html b/docs/external.html index 2895ffa8b..b7d2ddc56 100644 --- a/docs/external.html +++ b/docs/external.html @@ -6677,6 +6677,63 @@ valign="top" align="left"> Commercial + + +

+ + Virtual Ant +

+

+ Instead of manually creating build scripts in XML, Virtual Ant provides a fully virtual file system + where you can run your tasks in real time and see the results. Everything that you do is recorded and + turned into an Ant build script. +

+ + + + + + + + + + + + + + + +
+ Compatibility: + + + Ant 1.6.5 onwards + +
+ URL: + + + http://www.placidsystems.com/virtualant/ + +
+ Contact: + + + support@placidsystems.com + +
+ License: + + Commercial; OpenSource licenses available too. +

diff --git a/xdocs/antlibs/svn/index.xml b/xdocs/antlibs/svn/index.xml index 705b30750..86dda6a72 100755 --- a/xdocs/antlibs/svn/index.xml +++ b/xdocs/antlibs/svn/index.xml @@ -67,4 +67,4 @@
- \ No newline at end of file + diff --git a/xdocs/bindownload.xml b/xdocs/bindownload.xml index c2687c58e..f799e3ef0 100644 --- a/xdocs/bindownload.xml +++ b/xdocs/bindownload.xml @@ -188,4 +188,4 @@ SHA1.

- \ No newline at end of file + diff --git a/xdocs/bugs.xml b/xdocs/bugs.xml index c69fee600..7ea20ad4c 100644 --- a/xdocs/bugs.xml +++ b/xdocs/bugs.xml @@ -1,171 +1,171 @@ - - - - - - Antoine Levy-Lambert - Bug database - - - -
-

- This page gives you some bookmarks to use the Bugzilla - Apache Bug Database. -

-

- This link issues.apache.org connects you - to the complete list of Apache Bug Database systems. -

- -

- If the current nightly build doesn't resolve your problem, it is - possible that someone else has reported the issue. It is time to - look at . This system is easy to use, and it will - let you search the - currently open and resolved bugs to see if your problem has - already been reported. If your problem has been reported, you can - see whether any of the developers have commented, suggesting - workarounds, or the reason for the bug, etc. Or you may have - information to add (see about creating and modifying bug reports - below), in which case, go right ahead and add the information. - If you don't have any additional information, you may just want - to vote for this bug, and perhaps - add yourself to the CC list to follow the progress - of this bug. -

-

Open Ant bugs by order of priority.

-

Open Ant bugs by number of votes.

- - - -

- Please read our document about problems - before deciding that there is an unreported - bug in Ant. -

-

- You have a few choices at this point. You can send - 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 - is time to create - a bug report, this is a simple operation in the bug database. - Please try to provide as much information as possible in order - to assist the developers in resolving the bug. Please try to enter - correct values for the various inputs when creating the bug, such - as which version of Ant you are running, and on which platform, - etc. Once the bug is created, you can also add attachments to - the bug report. -

-

- What information should you include in your bug report? The - easiest bugs to fix are those that are most easily reproducible, - so it is really helpful if you can produce a small test case that - exhibits the problem. In this case, you would attach the build file - and any other files necessary to reproduce the problem, probably - packed together in an archive. If you can't produce a test case, - you should try to include a snippet from your build file and the - relevant sections from the verbose or debug output from Ant. Try - to include the header information where Ant states the version, - the OS and VM information, etc. As debug output is likely to be - very large, it's best to remove any output that is not - relevant. Once the bug is entered into the bug database, you - will be kept informed by email about progress on the bug. If - you receive email asking for further information, please try to - respond, as it will aid in the resolution of your bug. -

-

- To create the bug report hit this - - link. -

- - - -

- Sometimes, you may find that Ant just doesn't do what you need it - to. It isn't a bug, as such, since Ant is working the way it is - supposed to work. Perhaps it is some additional functionality for - a task that hasn't been thought of yet, or maybe a completely new - task. For these situations, you will - want to raise an enhancement request. Enhancement requests - are managed using the same Apache Bug Database described above. - These are just a different type of bug report. If you look in the - bug database, you will see that one of the severity settings for - a bug is "Enhancement". Just fill the bug report in, - set the severity of the bug to "Enhancement", and - state in the description how you would like to have Ant enhanced. - Again, you should first check whether there are any existing - enhancment requests that cover your needs. If so, just add your - vote to these. -

-

- - Create an enhancement report - -

- - - -

- If you aren't satisfied with just filing a bug report, you can - try to find the cause of the problem and provide a fix yourself. - The best way to do that is by working with the latest code from Subversion. - Alternatively, you can work with the source code available from the - - source distributions. If you - are going to tackle the problem at this level, you may want to - 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 - 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 - dev mailing list, - prefix "[PATCH]" - to your message subject (this is also a good idea for - a subject line in the bug database). - Please include any relevant bug numbers. - Patch files should be created with the -u - option of the - diff or svn diff command. For - example:



- - diff -u Javac.java.orig Javac.java > javac.diffs



- - or, if you have source from Subversion:



- - svn diff Javac.java > javac.diffs



- - - Note: You should give your patch files meaningful names. - This makes it easier for developers who need to apply a number - of different patch files. -

- - - -
- - + + + + + + Antoine Levy-Lambert + Bug database + + + +
+

+ This page gives you some bookmarks to use the Bugzilla + Apache Bug Database. +

+

+ This link issues.apache.org connects you + to the complete list of Apache Bug Database systems. +

+ +

+ If the current nightly build doesn't resolve your problem, it is + possible that someone else has reported the issue. It is time to + look at . This system is easy to use, and it will + let you search the + currently open and resolved bugs to see if your problem has + already been reported. If your problem has been reported, you can + see whether any of the developers have commented, suggesting + workarounds, or the reason for the bug, etc. Or you may have + information to add (see about creating and modifying bug reports + below), in which case, go right ahead and add the information. + If you don't have any additional information, you may just want + to vote for this bug, and perhaps + add yourself to the CC list to follow the progress + of this bug. +

+

Open Ant bugs by order of priority.

+

Open Ant bugs by number of votes.

+ + + +

+ Please read our document about problems + before deciding that there is an unreported + bug in Ant. +

+

+ You have a few choices at this point. You can send + 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 + is time to create + a bug report, this is a simple operation in the bug database. + Please try to provide as much information as possible in order + to assist the developers in resolving the bug. Please try to enter + correct values for the various inputs when creating the bug, such + as which version of Ant you are running, and on which platform, + etc. Once the bug is created, you can also add attachments to + the bug report. +

+

+ What information should you include in your bug report? The + easiest bugs to fix are those that are most easily reproducible, + so it is really helpful if you can produce a small test case that + exhibits the problem. In this case, you would attach the build file + and any other files necessary to reproduce the problem, probably + packed together in an archive. If you can't produce a test case, + you should try to include a snippet from your build file and the + relevant sections from the verbose or debug output from Ant. Try + to include the header information where Ant states the version, + the OS and VM information, etc. As debug output is likely to be + very large, it's best to remove any output that is not + relevant. Once the bug is entered into the bug database, you + will be kept informed by email about progress on the bug. If + you receive email asking for further information, please try to + respond, as it will aid in the resolution of your bug. +

+

+ To create the bug report hit this + + link. +

+ + + +

+ Sometimes, you may find that Ant just doesn't do what you need it + to. It isn't a bug, as such, since Ant is working the way it is + supposed to work. Perhaps it is some additional functionality for + a task that hasn't been thought of yet, or maybe a completely new + task. For these situations, you will + want to raise an enhancement request. Enhancement requests + are managed using the same Apache Bug Database described above. + These are just a different type of bug report. If you look in the + bug database, you will see that one of the severity settings for + a bug is "Enhancement". Just fill the bug report in, + set the severity of the bug to "Enhancement", and + state in the description how you would like to have Ant enhanced. + Again, you should first check whether there are any existing + enhancment requests that cover your needs. If so, just add your + vote to these. +

+

+ + Create an enhancement report + +

+ + + +

+ If you aren't satisfied with just filing a bug report, you can + try to find the cause of the problem and provide a fix yourself. + The best way to do that is by working with the latest code from Subversion. + Alternatively, you can work with the source code available from the + + source distributions. If you + are going to tackle the problem at this level, you may want to + 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 + 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 + dev mailing list, + prefix "[PATCH]" + to your message subject (this is also a good idea for + a subject line in the bug database). + Please include any relevant bug numbers. + Patch files should be created with the -u + option of the + diff or svn diff command. For + example:



+ + diff -u Javac.java.orig Javac.java > javac.diffs



+ + or, if you have source from Subversion:



+ + svn diff Javac.java > javac.diffs



+ + + Note: You should give your patch files meaningful names. + This makes it easier for developers who need to apply a number + of different patch files. +

+ + + +
+ + diff --git a/xdocs/contributors.xml b/xdocs/contributors.xml index 69e7c62a8..34b28ec7e 100644 --- a/xdocs/contributors.xml +++ b/xdocs/contributors.xml @@ -380,4 +380,4 @@ and EJB runtime environments -- in that order.

- \ No newline at end of file + diff --git a/xdocs/faq.xml b/xdocs/faq.xml index ac580e944..00452ee2e 100644 --- a/xdocs/faq.xml +++ b/xdocs/faq.xml @@ -1784,4 +1784,4 @@ mv /tmp/foo $ANT_HOME/bin/antRun - \ No newline at end of file + diff --git a/xdocs/mail.xml b/xdocs/mail.xml index 64c79e236..887023470 100644 --- a/xdocs/mail.xml +++ b/xdocs/mail.xml @@ -115,4 +115,4 @@ - \ No newline at end of file + diff --git a/xdocs/projects.xml b/xdocs/projects.xml index 497746369..a0ff594f5 100644 --- a/xdocs/projects.xml +++ b/xdocs/projects.xml @@ -642,4 +642,4 @@ - \ No newline at end of file + diff --git a/xdocs/srcdownload.xml b/xdocs/srcdownload.xml index 491a474ea..a686b93f6 100644 --- a/xdocs/srcdownload.xml +++ b/xdocs/srcdownload.xml @@ -185,4 +185,4 @@ SHA1.

- \ No newline at end of file + diff --git a/xdocs/stylesheets/site.vsl b/xdocs/stylesheets/site.vsl index ce9973bf0..b481eef4d 100644 --- a/xdocs/stylesheets/site.vsl +++ b/xdocs/stylesheets/site.vsl @@ -175,4 +175,4 @@ #footer() -#end \ No newline at end of file +#end diff --git a/xdocs/svn.xml b/xdocs/svn.xml index 9f4985e07..9af75b495 100644 --- a/xdocs/svn.xml +++ b/xdocs/svn.xml @@ -63,4 +63,4 @@ svn co http://svn.apache.org/repos/asf/ant/[project]/trunk/ ant-[project] - \ No newline at end of file +