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 12:27:25 GMT


Maarten Coene commented on IVY-531:

I agree with you Xavier, I was showing an alternative if you really wanted to use a path refid
to load the plugins...

I think the <classpath> element in <ivy:settings> could be usefull in the following
- you have different settings with different plugins (for instance, a resolve-only-settings
with pluginA and a publish-settings with pluginB). It could be usefull sometimes to load the
settings with different classpaths, especially if both plugins depend on different revisions
of the same module (like pluginA depends on http-client-2.x en pluginB depends on http-client-3.x)
- you use Ivy to resolve the plugins (and their dependencies). For instance, you could a kind
of "bootstrap"-settings to resolve your plugins with ivy:cachepath, and with that classpath
initialize another settings containing your plugins.
But that's indeed out of the scope for this issue, and there is an easy workaround: just convert
the Ant path into a ':' separated list (using  the pathconvert task for instance) and pass
that to Ivy when loading the settings.

One thing we should take care of is the choice of the path-separator. Will we always take
':' as separator, or ';' or will we use the system default, or will we allow the user to specify
the separator:

    <classpath path="path/jar1.jar:path/jar2.jar" pathsep=":" />

> 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