ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Trump (JIRA)" <>
Subject [jira] Updated: (IVY-531) ivyconf: <classpath/> to accept complex path
Date Fri, 04 Apr 2008 06:15:24 GMT


Jason Trump updated IVY-531:

    Attachment: ivy-531-r644587.patch

very true, consistency is best.  attached is a revised version of the patch that adds path
support to Ivy standalone, with consistent behavior with or without Ant.  the patch is against
today's trunk, revision 644587.

IvyClassLoaderManagerImpl has absorbed much code from IvyAntClassLoaderManager.  The code
is just a little trickier than what I had originally imagined, so I tried to add some more
unit test coverage to make up for it.

> 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-531-r644587.patch, 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