Comments on: Ivy Dependency Management – Lessons Learned and Ant 1.8 Mapped Resources http://www.beilers.com/2010/06/ivy-dependency-management-lessons-learned-and-ant-1-8-mapped-resources/?utm_source=rss&utm_medium=rss&utm_campaign=ivy-dependency-management-lessons-learned-and-ant-1-8-mapped-resources Crazy Thoughts on Software Development and Life in General Sat, 07 Jan 2012 03:56:19 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Mark http://www.beilers.com/2010/06/ivy-dependency-management-lessons-learned-and-ant-1-8-mapped-resources/#comment-53 Mark Tue, 13 Jul 2010 00:07:59 +0000 http://www.beilers.com/?p=696#comment-53 Damn, shoulda finshed reading the post :) Although i'm still not sure I'd separate them. The build stuff seems obvious enough, but there aren't a lot of them. The test stuff is less clearly seperated. Some if my test dependencies are clearly seperate (junit) but many are a result of what the code itself is using (say communications libraries). The only thing I can think of is having build tools as one (tiny) ivy file, the main app as a second, and the test deps as a third, with it depending on the "runtime" config of the main one, but that obviously isn't what you're doing. Damn, shoulda finshed reading the post :)

Although i’m still not sure I’d separate them. The build stuff seems obvious enough, but there aren’t a lot of them. The test stuff is less clearly seperated. Some if my test dependencies are clearly seperate (junit) but many are a result of what the code itself is using (say communications libraries). The only thing I can think of is having build tools as one (tiny) ivy file, the main app as a second, and the test deps as a third, with it depending on the “runtime” config of the main one, but that obviously isn’t what you’re doing.

]]> By: Mark http://www.beilers.com/2010/06/ivy-dependency-management-lessons-learned-and-ant-1-8-mapped-resources/#comment-52 Mark Tue, 13 Jul 2010 00:00:24 +0000 http://www.beilers.com/?p=696#comment-52 Why use multiple files? I just use multiple configs. I've got one config for each major subsystem, one for runtime, one for tests, one for build tools themselves. Then I just use ivy:cachepath to get create classpathes for each item, and only "retrieve" the runtime configuration. The only serious minus to this is it means I have to run ivy as part of every build. but as long as I have it configured to cache "latest" versions (so it doesn't have to constantly talk to the server) it only takes about 10 seconds to resolve all my dependencies, and I've literally got more than 100, and close to 200 when you include transitive deps (yes, the project is a mess :) ). Why use multiple files? I just use multiple configs. I’ve got one config for each major subsystem, one for runtime, one for tests, one for build tools themselves. Then I just use ivy:cachepath to get create classpathes for each item, and only “retrieve” the runtime configuration. The only serious minus to this is it means I have to run ivy as part of every build. but as long as I have it configured to cache “latest” versions (so it doesn’t have to constantly talk to the server) it only takes about 10 seconds to resolve all my dependencies, and I’ve literally got more than 100, and close to 200 when you include transitive deps (yes, the project is a mess :) ).

]]>