Return-Path: 
 <notifications-return-13468-apmail-ant-notifications-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org
Received: (qmail 42190 invoked from network); 23 Aug 2010 17:58:55 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 23 Aug 2010 17:58:55 -0000
Received: (qmail 67055 invoked by uid 500); 23 Aug 2010 17:58:55 -0000
Delivered-To: apmail-ant-notifications-archive@ant.apache.org
Received: (qmail 67026 invoked by uid 500); 23 Aug 2010 17:58:55 -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 67019 invoked by uid 99); 23 Aug 2010 17:58:55 -0000
Received: from Unknown (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Aug 2010 17:58:55 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Aug 2010 17:58:38 +0000
Received: from thor (localhost [127.0.0.1])
	by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o7NHwGOW009594
	for <notifications@ant.apache.org>; Mon, 23 Aug 2010 17:58:16 GMT
Message-ID: <3602098.513031282586296052.JavaMail.jira@thor>
Date: Mon, 23 Aug 2010 13:58:16 -0400 (EDT)
From: =?utf-8?Q?Nicolas_Lalev=C3=A9e_=28JIRA=29?= <jira@apache.org>
To: notifications@ant.apache.org
Subject: [jira] Resolved: (IVYDE-230) Shared Javadoc/Source attachments
In-Reply-To: <1704820334.186161263319796631.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


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

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

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

Actually I said "this is not possible with the current IvyDE implementation=
.", meaning without a patch.
Then thanks for the patch Gregory !

> Shared Javadoc/Source attachments
> ---------------------------------
>
>                 Key: IVYDE-230
>                 URL: https://issues.apache.org/jira/browse/IVYDE-230
>             Project: IvyDE
>          Issue Type: Improvement
>          Components: classpath container
>    Affects Versions: 2.0.0.final
>         Environment: Eclipse 3.3, IvyDE (2.0.0.final), Ivy (2.1.0.final)
>            Reporter: Jason A. Guild
>            Assignee: Nicolas Lalev=C3=A9e
>            Priority: Minor
>             Fix For: 2.2.0
>
>         Attachments: ivyde.patch
>
>
> It would be nice if IvyDE could attach javadoc artifacts to more than one=
 jar that is published by a module.
> For example, consider a rather large module called 'foo'. It has multiple=
 parts and pieces, some of which may not be required for your particular ap=
plication. The 'foo' module publishes multiple JAR artifacts:
> foo-a.jar
> foo-b.jar
> foo-c.jar
> The 'foo' module, however, is unfortunately /closed/ and the javadocs are=
 provided to the developer in one large archive 'foo-doc.zip'.
> We are using the default URL resolver against an Ivy repo located on our =
dev web server.
> The artifact pattern we are using in our ivy settings is:
> <artifact pattern=3D"http://XXXXXX/dev-repo/[organisation]/[module]/[revi=
sion]/[artifact]-[revision](-[classifier]).[ext]" />=20
> After modifying the ivy.xml file for the 'foo' module to publish the docs=
 via: <artifact name=3D"foo" type=3D"javadoc" ext=3D"zip" conf=3D"default" =
e:classifier=3D"doc"/>. IvyDE/Ivy will then happily pull down the javadoc a=
long with all the other artifacts. But, none of the foo-a, foo-b, or foo-c =
artifacts will have javadoc attachments in Eclipse (presumably because thei=
r artifact basenames do not match).
> Reorganizing the documentation into separate archives is not easy (or eve=
n possible) without the source code. Therefore, it would be nice if IvyDE c=
ould treat the single supplied javadoc artifact as a candidate for attachme=
nt on each of the component JAR artifacts without having to fetch the (poss=
ibly large) javadoc archive multiple times under different basenames.

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.