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

Gregory Fernandez updated IVYDE-230:
------------------------------------

    Attachment: ivyde.patch

In fact :

If a module declares only 1 source, on only 1 javadoc artifact, this artifact is associated with all jar artifacts ...

This patch is a svn diff againt latest trunk

> 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
>            Priority: Minor
>         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 application. 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="http://XXXXXX/dev-repo/[organisation]/[module]/[revision]/[artifact]-[revision](-[classifier]).[ext]" /> 
> After modifying the ivy.xml file for the 'foo' module to publish the docs via: <artifact name="foo" type="javadoc" ext="zip" conf="default" e:classifier="doc"/>. IvyDE/Ivy will then happily pull down the javadoc along 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 their artifact basenames do not match).
> Reorganizing the documentation into separate archives is not easy (or even possible) without the source code. Therefore, it would be nice if IvyDE could treat the single supplied javadoc artifact as a candidate for attachment on each of the component JAR artifacts without having to fetch the (possibly large) javadoc archive multiple times under different basenames.

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