[
https://issues.apache.org/jira/browse/MAPREDUCE-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792750#action_12792750
]
Todd Lipcon commented on MAPREDUCE-1114:
----------------------------------------
bq. So without fundamentally changing how dependencies are resolved, attacking
the problem as in the current patch is the only way to effect a meaningful
reduction
Yes, as far as I'm aware, that's the case. Thanks for the concise way of
explaining it.
To be completely honest, I'm nowhere near an expert in ant/ivy/maven/etc. I'm
just a developer who doesn't use an IDE, and waiting 30-40 seconds every time I
need to rerun a testcase got aggravating ;-)
bq. Is there a JIRA tracking progress in removing ivy?
I'm not aware of any such.
> Speed up ivy resolution in builds with clever caching
> -----------------------------------------------------
>
> Key: MAPREDUCE-1114
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1114
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.22.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Minor
> Attachments: mapreduce-1114.txt, mapreduce-1114.txt,
> mapreduce-1114.txt
>
>
> An awful lot of time is spent in the ivy:resolve parts of the build, even
> when all of the dependencies have been fetched and cached. Profiling showed
> this was in XML parsing. I have a sort-of-ugly hack which speeds up
> incremental compiles (and more importantly "ant test") significantly using
> some ant macros to cache the resolved classpaths.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
