[ https://issues.apache.org/jira/browse/IVY-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Trump updated IVY-531: ---------------------------- Attachment: ivy-ant-classpath.patch We needed this feature too, so I tried to implement it. Attached is a patch against today's trunk including test and documentation. What do you think? The patch adds two optional attributes to <classpath>, refid and path. The new attributes only work when Ivy is loaded from an Ant build script. For example, {quote} <ivysettings> <!-- references an ant path by id --> <classpath refid="my.ant.path"/> <!-- use a complex path expression --> <classpath path="path/jar1.jar:path/jar2.jar"/> ... </ivysettings> {quote} The 'url' and 'file' attributes still work exactly as they did before. Before you run the unit tests in the patch, you have to generate some new test jar files: bq. ant build-custom-resolver-jar > 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.