ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (IVYDE-146) source and javadoc attachment regression
Date Tue, 30 Dec 2008 10:18:44 GMT

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

Xavier Hanin resolved IVYDE-146.
--------------------------------

    Resolution: Fixed

I've fixed this issue, looking for source and javadoc artifacts in module descriptor again.
In the mean time I've slightly changed the way project dependencies are discovered, according
to my test it still works as before.

> source and javadoc attachment regression
> ----------------------------------------
>
>                 Key: IVYDE-146
>                 URL: https://issues.apache.org/jira/browse/IVYDE-146
>             Project: IvyDE
>          Issue Type: Bug
>          Components: classpath container
>    Affects Versions: 2.0.0.beta1
>            Reporter: Xavier Hanin
>            Assignee: Xavier Hanin
>             Fix For: 2.0.0.final
>
>
> In 2.0.0.beta1 version, the source and javadoc attachment does not work as well as before:
only artifacts got when resolving dependencies are used to find source and javadoc attachments,
while before IvyDE was looking for other artifacts declared by the module or even undeclared.
Looking for undeclared artifacts shouldn't be necessary anymore since now Ivy detects source
and javadoc artifacts on maven modules at parsing time, but requiring to actually resolve
source and javadoc artifacts as part of the resolve process is cumbersome.

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


Mime
View raw message