[
https://issues.apache.org/jira/browse/MAPREDUCE-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786309#action_12786309
]
Todd Lipcon commented on MAPREDUCE-1114:
----------------------------------------
When the classpath is resolved, it's written out to a text file named for that
variable. Then when it needs to be resolved again, if that file exists, it's
loaded rather than re-resolving.
> 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.
