At my previous company we were in the same situation. For a long time we managed our own extensive ivy respository. In the repository was a lot of open source software that we used. We also contributed many changes back to those open source projects, as much to relieve our own maintenance burden as out of pure generousity. The result was definitely a "win-win" situation.
Eventually it dawned on me that the repository meta-data itself could be "open sourced" and that's how Ivy RoundUp<http://code.google.com/p/ivyroundup/>was created. So if you believe in the principle of open source as a "win win" then I'd encourage you to (a) take advantage of all the work that has already been done for you in Ivy RoundUp, and (b) consider contributing back ivy meta-data for any additional modules, etc. you might be using. Note you can resolve against Ivy RoundUp plus your own repository in a blended fashion, so this is not an either/or choice. -Archie On Thu, Jun 18, 2009 at 11:36 AM, cquinn <[email protected]> wrote: > > Hi all. I'm just looking for some advice. > > I am in the process of migrating my company's multi-project build from a > system using plain Ant to one using Ivy. > > The current system has lots (140+) of 3rd-party jars, plus internal jars > checked into source control and dependencies fully listed in each of the > many projects' build files. I'm moving us to a system using Ivy 2 with POMs > or ivy metadata for Jars. > > It seems like it should be handy to leverage Maven POMs and repositories, > but in practice I'm having a lot of trouble with poorly spec'd dependencies > in the POMs available. I'm thinking it would be better to just create > ivy.xml files for all the Jars we use and correct/tune their dependencies. > > Does anyone have any experience with this? Any suggested resources? > > thanks > --carl > > -- > View this message in context: > http://www.nabble.com/Migrating-to-Ivy-tp24095311p24095311.html > Sent from the ivy-user mailing list archive at Nabble.com. > > -- Archie L. Cobbs
