You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by hi...@apache.org on 2014/10/26 19:32:11 UTC
svn commit: r1634376 - in /ant/site/ivy/production: download.html
get-involved.html write-doc.html
Author: hibou
Date: Sun Oct 26 18:32:10 2014
New Revision: 1634376
URL: http://svn.apache.org/r1634376
Log:
regenerate Ivy site
Modified:
ant/site/ivy/production/download.html
ant/site/ivy/production/get-involved.html
ant/site/ivy/production/write-doc.html
Modified: ant/site/ivy/production/download.html
URL: http://svn.apache.org/viewvc/ant/site/ivy/production/download.html?rev=1634376&r1=1634375&r2=1634376&view=diff
==============================================================================
--- ant/site/ivy/production/download.html (original)
+++ ant/site/ivy/production/download.html Sun Oct 26 18:32:10 2014
@@ -320,9 +320,9 @@ To get information about the different k
<h2>Old releases</h2>
Older releases of Apache Ivy can be found <a href="http://archive.apache.org/dist/ant/ivy/">here</a>. We highly recommend to not use those releases but upgrade to the latest release.<br class="xooki-br"/><br class="xooki-br"/><h2>Building from source</h2>
-What you can get here at the ASF is the latest sources from the Subversion repository:
+What you can get here at the ASF is the latest sources from the git repository:
<pre>
-svn co <a href="https://svn.apache.org/repos/asf/ant/ivy/core/trunk">https://svn.apache.org/repos/asf/ant/ivy/core/trunk</a> ivy
+git clone <a href="https://git-wip-us.apache.org/repos/asf/ant-ivy.git">https://git-wip-us.apache.org/repos/asf/ant-ivy.git</a>
</pre>
Then to build Apache Ivy from source, assuming you have Apache Ant™ 1.6.2+ and a jdk 1.5+ installed, then you only need to run the following command:
<pre>
Modified: ant/site/ivy/production/get-involved.html
URL: http://svn.apache.org/viewvc/ant/site/ivy/production/get-involved.html?rev=1634376&r1=1634375&r2=1634376&view=diff
==============================================================================
--- ant/site/ivy/production/get-involved.html (original)
+++ ant/site/ivy/production/get-involved.html Sun Oct 26 18:32:10 2014
@@ -297,7 +297,7 @@
<div id="main">
<h1 class="title">Get Involved</h1>
- <br class="xooki-br"/>As an Apache project, Apache Ivy™ is very open to external contributions.<br class="xooki-br"/><br class="xooki-br"/>There are many ways to contribute to Apache Ivy.<br class="xooki-br"/><br class="xooki-br"/>First, <a href="download.html">Download</a> and use it, subscribe to the <a href="mailing-lists.html">Mailing lists</a>, and answer other user questions. You can also browse <a href="issues.html">jira issues</a>, vote for the ones you are most interested in, and add your comments and feedback. You can also very easily contribute to the <a href="wiki.html">Wiki</a>.<br class="xooki-br"/><br class="xooki-br"/>When you browse the documentation, whenever you see something that could be improved, feel free to edit it and provide a documentation patch. It's very easy if you browse the documentation offline (in the doc directory if you check out Apache Ivy from svn), you will see a small toolbar at the upper right of the page, which allows you to
edit the page. Then all you have to do is attach your modification as a patch to a new issue in JIRA.<br class="xooki-br"/><i>If you are interested in contributing documentation, read <a href="write-doc.html">this page</a>.</i><br class="xooki-br"/><br class="xooki-br"/>You can also provide brand new documentation pages, tutorials, demos, or even links to a tutorial on your own blog. <br class="xooki-br"/><br class="xooki-br"/>Another useful way to contribute is to spread the word: if you like Apache Ivy, say it! On your blog, on other blog comments, on popular java related sites, wherever. The more popular Apache Ivy becomes, the more it will get external contributions, and the better it will be, for the benefit of the whole community.<br class="xooki-br"/><br class="xooki-br"/>When you get more confident with Apache Ivy, you can check it out from svn, and begin to see if there are issues you could fix or implement, and provide patches to allow the whole community to benefit from
your work.<br class="xooki-br"/><br class="xooki-br"/>When you provide a patch, to increase the chance to get integrated, do not forget to provide a junit test, and a patch to the documentation if it changes anything in Apache Ivy's behaviour.<br class="xooki-br"/><br class="xooki-br"/>And if you provide patches often, or answer many of the mailing list questions, you may get the chance to become a commiter, with write access to the svn repository!
+ <br class="xooki-br"/>As an Apache project, Apache Ivy™ is very open to external contributions.<br class="xooki-br"/><br class="xooki-br"/>There are many ways to contribute to Apache Ivy.<br class="xooki-br"/><br class="xooki-br"/>First, <a href="download.html">Download</a> and use it, subscribe to the <a href="mailing-lists.html">Mailing lists</a>, and answer other user questions. You can also browse <a href="issues.html">jira issues</a>, vote for the ones you are most interested in, and add your comments and feedback. You can also very easily contribute to the <a href="wiki.html">Wiki</a>.<br class="xooki-br"/><br class="xooki-br"/>When you browse the documentation, whenever you see something that could be improved, feel free to edit it and provide a documentation patch. It's very easy if you browse the documentation offline (in the doc directory if you check out Apache Ivy from git), you will see a small toolbar at the upper right of the page, which allows you to
edit the page. Then all you have to do is attach your modification as a patch to a new issue in JIRA.<br class="xooki-br"/><i>If you are interested in contributing documentation, read <a href="write-doc.html">this page</a>.</i><br class="xooki-br"/><br class="xooki-br"/>You can also provide brand new documentation pages, tutorials, demos, or even links to a tutorial on your own blog. <br class="xooki-br"/><br class="xooki-br"/>Another useful way to contribute is to spread the word: if you like Apache Ivy, say it! On your blog, on other blog comments, on popular java related sites, wherever. The more popular Apache Ivy becomes, the more it will get external contributions, and the better it will be, for the benefit of the whole community.<br class="xooki-br"/><br class="xooki-br"/>When you get more confident with Apache Ivy, you can check it out from git, and begin to see if there are issues you could fix or implement, and provide patches to allow the whole community to benefit from
your work.<br class="xooki-br"/><br class="xooki-br"/>When you provide a patch, to increase the chance to get integrated, do not forget to provide a junit test, and a patch to the documentation if it changes anything in Apache Ivy's behaviour.<br class="xooki-br"/><br class="xooki-br"/>And if you provide patches often, or answer many of the mailing list questions, you may get the chance to become a commiter, with write access to the git repository!
</div><!-- main -->
</td>
</tr>
Modified: ant/site/ivy/production/write-doc.html
URL: http://svn.apache.org/viewvc/ant/site/ivy/production/write-doc.html?rev=1634376&r1=1634375&r2=1634376&view=diff
==============================================================================
--- ant/site/ivy/production/write-doc.html (original)
+++ ant/site/ivy/production/write-doc.html Sun Oct 26 18:32:10 2014
@@ -297,9 +297,9 @@
<div id="main">
<h1 class="title">Contribute documentation</h1>
- <br class="xooki-br"/>Writing documentation for Apache Ivy™ is pretty simple.<br class="xooki-br"/><br class="xooki-br"/>The documentation engine used is called <a href="http://xooki.sourceforge.net">xooki</a>, and allows to edit pages while you browse them as soon as you browse them offline (and thus can actually save your modifications).<br class="xooki-br"/><br class="xooki-br"/>To browse the doc offline, we recommend to check it out from svn:
+ <br class="xooki-br"/>Writing documentation for Apache Ivy™ is pretty simple.<br class="xooki-br"/><br class="xooki-br"/>The documentation engine used is called <a href="http://xooki.sourceforge.net">xooki</a>, and allows to edit pages while you browse them as soon as you browse them offline (and thus can actually save your modifications).<br class="xooki-br"/><br class="xooki-br"/>To browse the doc offline, we recommend to check it out from git:
<pre>
-svn co <a href="https://svn.apache.org/repos/asf/ant/ivy/core/trunk/doc">https://svn.apache.org/repos/asf/ant/ivy/core/trunk/doc</a> ivy-doc
+git clone <a href="https://git-wip-us.apache.org/repos/asf/ant-ivy.git">https://git-wip-us.apache.org/repos/asf/ant-ivy.git</a>
</pre>
Alternatively you can also check out the whole site:
@@ -316,9 +316,9 @@ The source uses a format very familiar t
<pre>
<code><br class="xooki-br"/>any text including <tags/><br class="xooki-br"/></code>
</pre>
-Very helpful to avoid escaping all xml with lt and gt.<br class="xooki-br"/><br class="xooki-br"/>Finally, URLs are automatically recognized and convert to links, jira issues like <a href="http://issues.apache.org/jira/browse/IVY-202">IVY-202</a> are recognized too, and you can use a neat format to reference any ant ivy ant task like <a href="history/latest-milestone/use/install.html">install</a>, or also reference svn page easily like <a href="https://svn.apache.org/repos/asf/ant/ivy/core/trunk/build.xml">this link to build.xml</a>. And you can also link to another page by providing its id (i.e. its url without the base and the .html) like the <a href="index.html">Home</a> or the <a href="history/latest-milestone/index.html">Documentation (2.4.0-rc1)</a>.<br class="xooki-br"/><br class="xooki-br"/>Feel free to edit this page to get a good overview of what is possible.<br class="xooki-br"/><br class="xooki-br"/>And do not forget to save your changes before leaving the page! Then you
can use your favorite IDE or svn and compute a patch for what you changed, and submit this patch by attaching it to a jira issue, or simply sending it to the ivy-dev <a href="mailing-lists.html">mailing list</a>.<br class="xooki-br"/><br class="xooki-br"/><h1><a name="edit-toc"></a>Editing the TOC</h1>
+Very helpful to avoid escaping all xml with lt and gt.<br class="xooki-br"/><br class="xooki-br"/>Finally, URLs are automatically recognized and convert to links, jira issues like <a href="http://issues.apache.org/jira/browse/IVY-202">IVY-202</a> are recognized too, and you can use a neat format to reference any ant ivy ant task like <a href="history/latest-milestone/use/install.html">install</a>. And you can also link to another page by providing its id (i.e. its url without the base and the .html) like the <a href="index.html">Home</a> or the <a href="history/latest-milestone/index.html">Documentation (2.4.0-rc1)</a>.<br class="xooki-br"/><br class="xooki-br"/>Feel free to edit this page to get a good overview of what is possible.<br class="xooki-br"/><br class="xooki-br"/>And do not forget to save your changes before leaving the page! Then you can use your favorite IDE or git and compute a patch for what you changed, and submit this patch by attaching it to a jira issue, or simpl
y sending it to the ivy-dev <a href="mailing-lists.html">mailing list</a>.<br class="xooki-br"/><br class="xooki-br"/><h1><a name="edit-toc"></a>Editing the TOC</h1>
-The structure of the TOC is stored in the <a href="https://svn.apache.org/repos/asf/ant/ivy/core/trunk/doc/toc.json">toc.json</a>. Some operations are available in the toolbar, others need manual editing of the json file.<br class="xooki-br"/><br class="xooki-br"/><h2>Moving entries</h2>
+The structure of the TOC is stored in the toc.json. Some operations are available in the toolbar, others need manual editing of the json file.<br class="xooki-br"/><br class="xooki-br"/><h2>Moving entries</h2>
To move up or down an entry within its category, you can use the arrows in the toolbar. First go on the page you want to move and then use the arrows (<img src="xooki/images/up.gif" /> <img src="xooki/images/down.gif" />). Note that the changes are directly done in the json file, there is no need to trigger some "save" action.<br class="xooki-br"/><br class="xooki-br"/><h2>Adding entries</h2>