[
https://issues.apache.org/jira/browse/IVY-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990134#comment-12990134
]
Nicolas Lalevée commented on IVY-1235:
--------------------------------------
As you may have seen Maarten, IVYDE-56 tried to implement that feature for
Eclipse.
See the function maybeRetrieve in IvyResolver:
http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/org.apache.ivyde.eclipse/src/java/org/apache/ivyde/eclipse/resolve/IvyResolver.java?revision=1060436&view=markup
I would be great to have this functionality at the API level. I tried to
implement at that time but I was not enough confident because of some possible
API break I was making.
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
