You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Jason Trump (JIRA)" <ji...@apache.org> on 2008/04/03 21:51:25 UTC
[jira] Issue Comment Edited: (IVY-531) ivyconf: to
accept complex path
[ https://issues.apache.org/jira/browse/IVY-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585258#action_12585258 ]
tormp edited comment on IVY-531 at 4/3/08 12:49 PM:
----------------------------------------------------------
So I was thinking about providing an updated patch, and would like to make sure it does what it should based on this discussion. How does this sound:
Ivy standalone supports:
{noformat}
<!-- complex path, system default separator is used when no
pathsep is provided -->
<classpath path="path/p1.jar:path/p2.jar"/>
<!-- complex path, with an alternate path separator -->
<classpath path="p1.jar~p2.jar~http://url/also/ok.jar" pathsep="~"/>
{noformat}
Ivy + Ant supports:
{noformat}
<!-- refid loads a named path when Ivy is embedded -->
<classpath refid="some.path.id"/>
<!-- complex path supports any path that Ant does.
I can't decide if this is a good idea or not. Comments?
-->
<classpath path="p1.jar;p2.jar:p3.jar"/>
<!-- complex path with pathsep behaves exactly the same as standalone -->
<classpath path="p1.jar~p2.jar" pathsep="~"/>
{noformat}
was (Author: tormp):
So I was thinking about providing an updated patch, and would like to make sure it does what it should based on this discussion. How does this sound:
Ivy standalone supports:
<!-- complex path, system default separator is used when no pathsep is provided -->
<classpath path="path/p1.jar:path/p2.jar:http://url.is/also/supported.jar"/>
<!-- complex path, with an alternate path separator -->
<classpath path="p1.jar~p2.jar" pathsep="~"/>
Ivy + Ant supports:
<!-- refid loads a named path when Ivy is embedded -->
<classpath refid="some.path.id"/>
<!-- complex path supports any path that Ant does.
I can't decide if this is a good idea or not. Comments? -->
<classpath path="p1.jar;p2.jar:p3.jar"/>
<!-- complex path with pathsep behaves exactly the same as standalone -->
<classpath path="p1.jar~p2.jar" pathsep="~"/>
> ivyconf: <classpath/> to accept complex path
> --------------------------------------------
>
> Key: IVY-531
> URL: https://issues.apache.org/jira/browse/IVY-531
> 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.