[
https://issues.apache.org/jira/browse/IVY-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gintas Grigelionis updated IVY-632:
-----------------------------------
Description:
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 -> organisation = "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.
was:
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.
> 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 -> organisation = "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 was sent by Atlassian JIRA
(v6.4.14#64029)
