ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Trump (JIRA)" <>
Subject [jira] Commented: (IVY-531) ivyconf: <classpath/> to accept complex path
Date Sun, 30 Mar 2008 22:56:25 GMT


Jason Trump commented on IVY-531:

sorry it has taken me so long to respond to your comments -- i was waiting for a JIRA notification.
 I'll try to check back here more frequently.

thanks for reviewing my patch.  Only supporting complex paths from within Ant is definitely
a major limitation.  But when I looked at the amount of code that existed in Ant for parsing
paths and building classloaders, I got nervous about the idea of adding so much without a
good review.  I'd also be worried about adding <classpath> to <ivy:settings> in
a way that is different from <classpath> elements in other standard Ant tasks.

I thought that we could add support for 'path' in IvyClassLoaderManagerImpl like in Xavier's
first comment.  Maybe it wouldn't have to support the full Ant syntax (no automatic switching
between ';' and ':', for example)?

Regarding refid:  I thought in the future the "refid" syntax might be useful in more environments
than just Ant.  For example, when Ivy is used in Eclipse, refid could be used to refer to
the name of an Eclipse User Libraries or project build paths.

Interesting to note that Maarten's second bullet point is exactly what we are doing in our
build system.  We try to use Ivy to load its own plugins.   Thus we don't have to put plugin
jars in source control, or require developers to update them manually.  It is also useful
to have the plugin jars in the Ivy cache instead of using a URL classloader, so that remote
developers don't have to be on VPN to run the build.

> 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