ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason A. Guild (JIRA)" <>
Subject [jira] Created: (IVYDE-230) Shared Javadoc/Source attachments
Date Tue, 12 Jan 2010 18:09:56 GMT
Shared Javadoc/Source attachments

                 Key: IVYDE-230
             Project: IvyDE
          Issue Type: Improvement
          Components: classpath container
    Affects Versions:
         Environment: Eclipse 3.3, IvyDE (, Ivy (
            Reporter: Jason A. Guild
            Priority: Minor

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:


The 'foo' module, however, is unfortunately /closed/ and the javadocs are provided to the
developer in one large archive ''.

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.

View raw message