[
https://issues.apache.org/jira/browse/IVY-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644090#action_12644090
]
Xavier Hanin commented on IVY-742:
----------------------------------
That sounds like a much more flexible and interesting way to provide parent
import mechanism! While thinking about it, I'm wondering if using the parent
concept isn't limiting itself. Why wouldn't we call this import as the import
in Ant (or extends as we call it in EasyAnt)? Then we could imagine importing
multiple ivy files, controlling for each one what is really imported. More
flexible, and not really harder to implement and document if we fix what
happens when the same dependency is defined multiple times in imported modules
with different versions / conf mapping. I guess we could say that the last (or
first?) definition takes precedence.
WDYT?
> Support ivy.xml parent mechanism
> --------------------------------
>
> Key: IVY-742
> URL: https://issues.apache.org/jira/browse/IVY-742
> Project: Ivy
> Issue Type: New Feature
> Components: Core
> Environment: Any
> Reporter: Neil Lott
>
> Here's the email that details this feature:
> On Thu, Feb 21, 2008 at 11:22 PM, Neil Lott <[EMAIL PROTECTED]>
> wrote:
> Let's say I have multiple modules each with their own ivy.xml
> <ivy-module version="2.0">
> <info organisation="${organization.name}" module="$
> {interface.jar.prefix}"/>
> <configurations>
> <conf name="interface" description="dependencies for
> interface"/>
> <include file="path/to/included-configurations.xml"/>
> </configurations>
> <publications>
> <artifact name="${interface.jar.prefix}" type="jar"
> conf="interface" ext="jar"/>
> </publications>
> <dependencies>
> <dependency org="twc" name="mas-core" rev="${mas.version}"
> conf="interface->server"/>
> </dependencies>
> </ivy-module>
> and I want them all to share an inherited configuration found in a
> file: included-configurations.xml
> <configuration>
> <conf name="test"/>
> </configuration>
> <dependencies>
> <dependency name="testng" rev="5.7" conf="test"/>
> </dependencies>
> so in the inherited configurations file I'd also like to include a
> dependency that goes along with that configuration.
> Is something like this possible?
> No, this is not possible in Ivy, but you can use text or xml processing
> tools to recompose your Ivy file before asking Ivy to resolve the
> dependencies of your module.
> Alternatively, since what you ask is close to maven 2 parent mechanism, I
> think it could be a nice addition to Ivy feature set. So feel free to open
> an issue, and even provide a patch :-)
> Xavier
> Thanks,
> Neil
> --
> Xavier Hanin - Independent Java Consultant
> http://xhab.blogspot.com/
> http://ant.apache.org/ivy/
> http://www.xoocode.org/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
