Return-Path: 
 <notifications-return-15712-apmail-ant-notifications-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org
Received: (qmail 14046 invoked from network); 3 Apr 2011 14:38:44 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 3 Apr 2011 14:38:44 -0000
Received: (qmail 51195 invoked by uid 500); 3 Apr 2011 14:38:44 -0000
Delivered-To: apmail-ant-notifications-archive@ant.apache.org
Received: (qmail 51165 invoked by uid 500); 3 Apr 2011 14:38:43 -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 51155 invoked by uid 99); 3 Apr 2011 14:38:43 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 03 Apr 2011 14:38:43 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 03 Apr 2011 14:38:42 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id B0D6590847
	for <notifications@ant.apache.org>; Sun,  3 Apr 2011 14:38:05 +0000 (UTC)
Date: Sun, 3 Apr 2011 14:38:05 +0000 (UTC)
From: =?utf-8?Q?Nicolas_Lalev=C3=A9e_=28JIRA=29?= <jira@apache.org>
To: notifications@ant.apache.org
Message-ID: 
 <1751088636.31216.1301841485706.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <28730894.141631289986033341.JavaMail.jira@thor>
Subject: [jira] [Resolved] (IVYDE-267) Allow specifying source and javadoc
 mapping on binaries directly in the ivy.xml
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/IVYDE-267?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nicolas Lalev=C3=A9e resolved IVYDE-267.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: trunk
         Assignee: Nicolas Lalev=C3=A9e

I finally implemented an IvyDE namespace

> Allow specifying source and javadoc mapping on binaries directly in the i=
vy.xml
> -------------------------------------------------------------------------=
------
>
>                 Key: IVYDE-267
>                 URL: https://issues.apache.org/jira/browse/IVYDE-267
>             Project: IvyDE
>          Issue Type: New Feature
>            Reporter: Nicolas Lalev=C3=A9e
>            Assignee: Nicolas Lalev=C3=A9e
>             Fix For: trunk
>
>
> IvyDE tries to automatically guess which source artifact corespond to the=
 binary ones so they get proper attachement with Eclipse. Sometimes IvyDE c=
annot guess easily. Maybe the information could be provided directly by the=
 module descriptor, with some extra metadata.
> For instance we could imagine a ivyde namespace and this:
> {code:xml}
> <?xml version=3D"1.0" encoding=3D"UTF-8"?>
> <ivy-module version=3D"2.0" xmlns:ivyde=3D"http://ant.apache.org/ivy/ivyd=
e/ns/">
>     <info organisation=3D"myorg" module=3D"mymodule" revision=3D"1.0" />
>     <configurations>
>     ...
>     </configurations>
>     <publications>
>         <artifact name=3D"myjar"      type=3D"jar"    ext=3D"jar" ivyde:s=
ource=3D"mysources" ivyde:javadoc=3D"myjavadocs" />
>         <artifact name=3D"mysources"  type=3D"source" ext=3D"jar" />
>         <artifact name=3D"myjavadocs" type=3D"javadoc" ext=3D"jar" />
>     </publications>
>     <dependencies>
>     ...
>     </dependencies>
> </ivy-module>
> {code}
> Another proposal from [Gerard Fernandes|https://issues.apache.org/jira/br=
owse/IVYDE-265?focusedCommentId=3D12932868&page=3Dcom.atlassian.jira.plugin=
.system.issuetabpanels%3Acomment-tabpanel#action_12932868]:
> {quote}
> One way to specify this would be the use of XML id and idref attributes (=
because these can be enforced by XSD schemas, if ivy.xml eventually goes to=
 schema validation).
> e.g. the following (note the hack renaming the source file to mimic the b=
inary artifact name):
> <dependency org=3D"org.junit" name=3D"junit" rev=3D"4.8.2" conf=3D"TEST->=
default">
> <artifact name=3D"junit-dep" />
> <artifact name=3D"junit-dep" type=3D"src" ext=3D"zip" />
> </dependency>
> could be re-written as:
> <dependency org=3D"org.junit" name=3D"junit" rev=3D"4.8.2" conf=3D"TEST->=
default">
> <artifact id=3D"junit" name=3D"junit-dep" />
> <artifact idref=3D"junit" name=3D"junit" type=3D"src" ext=3D"zip" />
> </dependency>
> or:
> <dependency org=3D"org.junit" name=3D"junit" rev=3D"4.8.2" conf=3D"TEST->=
default">
> <artifact name=3D"junit-dep" src-ref=3D"junit-src" />
> <artifact id=3D"junit-src" name=3D"junit" type=3D"src" ext=3D"zip" />
> </dependency>
> {quote}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira