[
https://issues.apache.org/jira/browse/IVY-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992770#comment-12992770
]
Nicolas Lalevée commented on IVY-1235:
--------------------------------------
That's better but not sufficient: we need the mapping between the artifact and
the file so IvyDE can properly bind a source on the jar for instance.
I have made the modification in r1069157.
Note that I didn't make any change in IvyDE so it doesn't require now Ivy 2.3.
So people could still install it with earlier Ivy. Once we choose IvyDE to
require Ivy 2.3, we will then use this cleaner API.
Thanks !
> 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
> Fix For: trunk
>
>
> 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
