[
http://issues.apache.org/jira/browse/IVY-354?page=comments#action_12458171 ]
John Williams commented on IVY-354:
-----------------------------------
Ok, I understand how the post-resolve tasks work now, and I discovered that by
setting ${ivy.organisation} and ${ivy.module} I don't need to set those
attributes individually on each post-resolve task. Knowing that solves 90% of
my concerns, but I still think Ivy could be made more user-friendly by
modifying the resolve task itself. If I had known what I know now, I would
have asked for this:
Add a "useCache" attribute to <ivy:resolve>, with a default of "false".
Running <ivy:resolve> would unconditionally parse the ivy.xml file to get the
values of ${ivy.organisation}, ${ivy.module}, ${ivy.revision} and
${ivy.resolved.configurations}. Next, if useCache=true, the cache would be
checked for the appropriate data files. If the cache files exist and are newer
than the ivy.xml file, the task would stop. Otherwise the task would complete
as it does now.
This is all well within the scope of what I could implement myself if you think
it's a reasonable feature to add.
> add option to cache results of ivy:resolve
> ------------------------------------------
>
> Key: IVY-354
> URL: http://issues.apache.org/jira/browse/IVY-354
> Project: Ivy
> Issue Type: Wish
> Components: Core
> Affects Versions: 1.4.1
> Environment: all
> Reporter: John Williams
>
> Using ivy:cachepath is a nice alternative to ivy:retrieve, but doing a
> resolve on every build is too slow. If there were some way to cache the
> result of resolving it would make cachepath much more pleasant to use.
> I've been experimenting with a poor man's version of this by saving the
> classpaths in a properties file to avoid needing to use Ivy so much, but this
> solution seems clumsy because it requires many steps.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
