[
https://issues.apache.org/jira/browse/IVY-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829167#action_12829167
]
randy baron commented on IVY-1086:
----------------------------------
We have the same problem. It doesn't seem to be possible (although we're still
working on it) with our current source structure to use ivy. Perhaps there is
another way ivy expects projects to be laid out? It would be very nice if this
module check considered the extra attributes.
> 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.
-
You can reply to this email to add a comment to the issue online.
