[
https://issues.apache.org/jira/browse/IVY-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537657
]
Xavier Hanin commented on IVY-632:
----------------------------------
There's a workaround when you control your repository: use namespaces to keep
the same organization.
But I agree this would be useful if you really changed your mind for the
organization name. What could be done is put a file in the repository saying
where the organization has been relocated, and when (which version). Kind of
redirect.
> support changing organisations
> ------------------------------
>
> Key: IVY-632
> URL: https://issues.apache.org/jira/browse/IVY-632
> Project: Ivy
> Issue Type: New Feature
> Components: Core
> Reporter: Maarten Coene
>
> It is possible that the organisation has been changed when a new version of a
> module is released.
> For instance:
> ant 1.6.x -> organisation = "ant"
> ant 1.7.x -> orgnaisation = "org.apache.ant"
> This makes it difficult when you have dynamic revisions like this:
> <dependency org="ant" module="ant" rev="[1.6, 1.7]" />
> which will only find the latest 1.6.x revision
> It would be a nice feature if this use case could be supported by Ivy.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
