Return-Path: 
 <notifications-return-15711-apmail-ant-notifications-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org
Received: (qmail 9517 invoked from network); 3 Apr 2011 14:36:10 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 3 Apr 2011 14:36:10 -0000
Received: (qmail 49557 invoked by uid 500); 3 Apr 2011 14:36:10 -0000
Delivered-To: apmail-ant-notifications-archive@ant.apache.org
Received: (qmail 49532 invoked by uid 500); 3 Apr 2011 14:36:10 -0000
Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:notifications-help@ant.apache.org>
List-Unsubscribe: <mailto:notifications-unsubscribe@ant.apache.org>
List-Post: <mailto:notifications@ant.apache.org>
List-Id: <notifications.ant.apache.org>
Reply-To: dev@ant.apache.org
Delivered-To: mailing list notifications@ant.apache.org
Received: (qmail 49525 invoked by uid 99); 3 Apr 2011 14:36:10 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 03 Apr 2011 14:36:10 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_FRT_BELOW2
X-Spam-Check-By: apache.org
Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 03 Apr 2011 14:36:07 +0000
Received: by eris.apache.org (Postfix, from userid 65534)
	id 4C8602388980; Sun,  3 Apr 2011 14:35:45 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r1088317 - /ant/ivy/ivyde/trunk/doc/cpc/jarmapping.html
Date: Sun, 03 Apr 2011 14:35:45 -0000
To: notifications@ant.apache.org
From: hibou@apache.org
X-Mailer: svnmailer-1.0.8
Message-Id: <20110403143545.4C8602388980@eris.apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org

Author: hibou
Date: Sun Apr  3 14:35:44 2011
New Revision: 1088317

URL: http://svn.apache.org/viewvc?rev=1088317&view=rev
Log:
IVYDE-267
 - add the documentation about the new namespace

Modified:
    ant/ivy/ivyde/trunk/doc/cpc/jarmapping.html

Modified: ant/ivy/ivyde/trunk/doc/cpc/jarmapping.html
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/cpc/jarmapping.html?rev=1088317&r1=1088316&r2=1088317&view=diff
==============================================================================
--- ant/ivy/ivyde/trunk/doc/cpc/jarmapping.html (original)
+++ ant/ivy/ivyde/trunk/doc/cpc/jarmapping.html Sun Apr  3 14:35:44 2011
@@ -28,11 +28,11 @@ Apache IvyDE will resolve the dependenci
 
 <h1>Finding jars types</h1>
 
-There are three types of jars handled by Eclipse&#153;:
+There are three types of jars handled by Eclipse":
 <ul>
     <li>the binary jars: they will be added to the classpath in oder to compile and run; they contain the .class files.</li>
     <li>the source jars/zip: they will be bound to the binary one to browse dependency sources; they are basically a zip of .java files</li>
-    <li>the javadoc jars/zip: they will be bound to the binary one to browse the API documentation of the dependencies of your project; they are a zip of .html files respectin a layout produced by javadoc.</li>
+    <li>the javadoc jars/zip: they will be bound to the binary one to browse the API documentation of the dependencies of your project; they are a zip of .html files respectively in a layout produced by javadoc.</li>
 </ul>
 
 To find the binary jars, Apache IvyDE is relying on the "Accepted types" preference field you can find in the <a href="create.html">container configuration panel</a>, or in the <a href="../preferences.html#classpath">global one</a>. If the artifact has a type listed here, it is then added to the classpath.
@@ -43,12 +43,27 @@ For the javadocs, it is relying on the "
 
 <h1>Binding the jars</h1>
 
-The second step is to bind a source artifact with a binary one. Apache IvyDE has the folowing algorithm:
+<h2>Alorithm</h2>
+
+The second step is to bind a source artifact with a binary one. IvyDE has the following algorithm:
 <ul>
-    <li>first if a binary jar has the same artifact name than a source one, there are bound together.</li>
+    <li>first, it looks up for a specified name in the ivy.xml via the "ivyde" namespace (see bellow)</li>
+    <li>next, if a binary jar has the same artifact name than a source one, there are bound together.</li>
     <li>if none matched, then IvyDE search for sources which have one of the suffix specified in "Sources suffixes".</li>
 </ul>
 
+<h2>The IvyDE namespace</h2>
+
+In the ivy.xml file in your repository, you can specifically bind a binary artifact to a source one and to a javadoc one, so IvyDE knows for sure which bind to the other.
+
+In the <a href="http://ant.apache.org/ivy/history/latest-milestone/ivyfile/artifact.html">artifact</a> element, you can specify:
+<ul>
+<li><tt>ivyde:source="my-source-artifact-name"</tt> which specify the artifact name of the source to bind to the current binary one</li>
+<li><tt>ivyde:javadoc="my-javadoc-artifact-name"</tt> which specify the artifact name of the javadoc to bind to the current binary one</li>
+</ul>
+
+<h2>Exemples</h2>
+
 For instance, searching for the sources of mylib.jar (type=jar), with the default value of "Sources suffixes" ("-source,-sources,-src"), IvyDE will look to bind it to the first one existing of:
 <ul>
 <li>mylib.jar (type=source)</li>
@@ -59,7 +74,27 @@ For instance, searching for the sources 
 
 Note that Apache IvyDE don't care about the extension, it can be .zip too.
 
-Same apply for javadocs with respectively "Javadocs suffixes".</textarea>
+Same apply for javadocs with respectively "Javadocs suffixes".
+
+<hr />
+
+With the IvyDE namespace, having the ivy.xml file:
+<code>
+<ivy-module version="2.0" xmlns:ivyde="http://ant.apache.org/ivy/ivyde/ns/">
+    <info organisation="com.acme" module="mylib" />
+    <publications>
+        <artifact name="mylib" type="jar" ext="jar" ivyde:source="the-sources-of-mylib" ivyde:javadoc="the-javadoc-of-mylib" />
+        <artifact name="the-sources-of-mylib" type="source" ext="jar" />
+        <artifact name="the-javadoc-of-mylib" type="javadoc" ext="jar" />
+    </publications>
+</ivy-module>
+</code>
+
+Without furether setup in IvyDE preferences pages, IvyDE will bind:
+<ul>
+<li>the jar <tt>the-sources-of-mylib</tt> as sources of the jar <tt>mylib</tt></li>
+<li>the jar <tt>the-javadoc-of-mylib</tt> as javadoc of the jar <tt>mylib</tt></li>
+</ul></textarea>
 <script type="text/javascript">xooki.postProcess();</script>
 </body>
 </html>