[jira] [Commented] (IVY-1086) Resolve failed when a module depends on a module with same module name which differs in extra attributes

["Tom Howard (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IVY-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13667499#comment-13667499 ] 

Tom Howard commented on IVY-1086:
---------------------------------

This is also a problem trying to model dependencies for third-party modules that we don't have control over. i.e. we have a third-party modules with versions 5.7.0 and 5.7.1. Version 5.7.1 depends on 5.7.0. While I don't agree with having these sort of dependencies, they do exist and Ivy should support them.
                
> Resolve failed  when a module depends on a module with same module name which differs in extra attributes 
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: IVY-1086
>                 URL: https://issues.apache.org/jira/browse/IVY-1086
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.1.0-RC1
>            Reporter: Viola Deitermann
>            Priority: Critical
>
> If a module depends on itself (module name matches), an exception is
> thrown in Ivy, and resolve fails.
> But when a module differs in extra attributes, this could be a big problem.
> For example i have a module with organisation="myOrg" and module="test" and extra attribute e:component="compA"
> And i have a module with organisation ="myOrg" and module="test" and extra attribute e:component="compB"
> Now my module test from component B has a dependency on the module test fro component A, Ivy will throw an exception.
> I think Ivy should also compare the extra attributes, before it throws the exception: "a module is not
> authorized to depend on itself"
> We want to use Ivy, but we need the extra attributes by resolving.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira