You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Wolfgang Frank (JIRA)" <ji...@apache.org> on 2012/07/24 15:52:35 UTC

[jira] [Updated] (IVY-1366) Resolve does not deliver all dependent artifacts

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

Wolfgang Frank updated IVY-1366:
--------------------------------

    Attachment: IVY-1366.zip

Example for this problem.
The testcase is ISH-1.
                
> Resolve does not deliver all dependent artifacts
> ------------------------------------------------
>
>                 Key: IVY-1366
>                 URL: https://issues.apache.org/jira/browse/IVY-1366
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.3.0-RC1
>            Reporter: Wolfgang Frank
>         Attachments: IVY-1366.zip
>
>
> We have three configurations.
> {code:title=Configurations}
> <configurations>
>    <conf name="runtime" extends="requires, compile" transitive="true"/>
>    <conf name="requires" />
>    <conf name="compile"/>
> </configurations>
> {code}
> Additional we have the following dependencies between ivy modules (test, a, b, c) (each module has a simple jar as artifact):
> {code:title=Dependencies}
> test "requires->#" a
> test "requires->#" c
> c "requires->#" a
> c "requires->#" b
> {code}
> The artifacts have the configuration compile.
> If I do a resolve on test with configuration "runtime" I only get artifacts for modules a and c but not b. 
> The problem happens in conflict resolution. Ivy generates the dependendies with wrong rootModuleConfigurations. In out case, the module b is loaded with root module configuration requires and not runtime.
> You find attached the example a unit test and a possible resolution in method computeConflicts of ResolveEngine.
> Possible dependency to IVY-729

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira