You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Maarten Coene (JIRA)" <ji...@apache.org> on 2011/01/29 11:54:43 UTC
[jira] Assigned: (IVY-1235) Generate classpath from retrieve
results, allow cachepath to take a repo path/pattern
[ https://issues.apache.org/jira/browse/IVY-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maarten Coene reassigned IVY-1235:
----------------------------------
Assignee: Maarten Coene
> Generate classpath from retrieve results, allow cachepath to take a repo path/pattern
> -------------------------------------------------------------------------------------
>
> Key: IVY-1235
> URL: https://issues.apache.org/jira/browse/IVY-1235
> Project: Ivy
> Issue Type: Improvement
> Components: Ant
> Affects Versions: 2.2.0-RC1
> Reporter: Dobes Vandermeer
> Assignee: Maarten Coene
> Priority: Minor
>
> Currently you can use the cachepath directive to generate a classpath that refers to the ivy cache.
> However, if you are generating a jar file manifest, this is not very useful.
> Instead, you want to generate a classpath for a bunch of jars relative to the jar you are creating.
> One way to make this easy would be to have ivy:retrieve have an option that causes it to also export a path similar to the way cachepath does. This path could then be used in the <jar> command to set the classpath on the jar file.
> Alternatively, cachepath could be changed so that it accepts a retrieve pattern and it applies that pattern to the resolved dependencies instead of using the ivy cache paths.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.