Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Won't Fix
-
0.22.0
-
None
-
None
Description
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.
Attachments
Attachments
Issue Links
- is related to
-
HADOOP-6366 Reduce ivy console output to ovservable level
- Closed