Any project that considers longevity or offline rebuilding must think about how to archive all their dependencies. What if the repositories go
away? What if a lawsuit forces some jar to be pulled. You may also need a private repository to store stuff that isnt in open source, or just not in the public repositories. This is no different from putting the JARs in a lib/ dir, except you have to make up stub poms that declare some or zero dependencies. ________________________________________________ >>A private repository being an "internal remote" repository on a machine that gets backed up nightly. >>Where's the harm in that? ________________________________________________ Being able to switch versions just by changing property files is nice... ________________________________________________ >>OMG - yes - I do miss this. ________________________________________________ I worry about its stability, though things are improving. The ant tasks can be a bit up and down from version to version, which implies they dont get tested enough. ________________________________________________ >> no kidding - this is the biggest shortcoming of m2 from my standpoint. M2 is about 1 - 1.5 years away from being really useful (and recently I've been forced into this world because.... ________________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
