ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maarten Coene (JIRA)" <>
Subject [jira] Commented: (IVY-531) ivyconf: <classpath/> to accept complex path
Date Tue, 25 Mar 2008 07:15:24 GMT


Maarten Coene commented on IVY-531:

I think we can support the path attribute, even when we run outside ant, it's just a separated
list of single files as I see it. No Ant-related code needed for this attribute.

The refid attribute is more Ant-related, so I'd rather keep it outside the settings. But perhaps
we can add support for a classpath-element to the settings task like this:

<ivy:settings ...>
    <classpath refid="my.ant.path" />


<ivy:settings ...>
       <pathelement ... />
       <pathelement ... />
       <path refid="..." />


> ivyconf: <classpath/> to accept complex path
> --------------------------------------------
>                 Key: IVY-531
>                 URL:
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Ant
>         Environment: Any
>            Reporter: Eric Crahen
>            Priority: Minor
>         Attachments: ivy-ant-classpath.patch
> Eric:
> The ivyconf.xml classpath tag accepts file or url elements which seem capable of pointing
to only a single classpath element, either a path or a jar. Can a full classpath be expressed?
> For instance, I would like to set an ant property called my.classpath and have it contain
something like "a.jar:b.jar:c.jar". I'd like to use that property in my ivyconf.xml in a classpath
element to set the classpath for resolver with complex dependencies
> Xavier:
> Sounds like a good idea, but this is not implemented yet. Open a jira issue.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message