ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IVY-531) ivyconf: <classpath/> to accept complex path
Date Thu, 03 Apr 2008 19:55:24 GMT

    [ https://issues.apache.org/jira/browse/IVY-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585262#action_12585262
] 

Xavier Hanin commented on IVY-531:
----------------------------------

I think I'd stick with pure compatibility between the two modes for the path / pathsep attributes.
Leveraging Ant path is smart, but I think we'll quickly run into users not understanding why
something work in a place and not in the other. If we really want to have support for any
ant path syntax, I'd rather go with an 'antpath' attribute or something like that.
Besides this everything sounds great!

> 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.


Mime
View raw message