2008/12/22 Brian E. Fox <[email protected]> > This isn't entirely true. You could miss dependencies that weren't > deployed,
I dont' understand how I could I miss dependencies that "weren't deployed". Because if they weren't deployed, CI local maven repository could never have retrieved those dependencies. Agreed if you rather speak about dependencies that was deployed some day, but are no more later that would stay in the CI local repo for ever. > or if you change your MRM config, you could miss a problem > there. It's better to have the CI system discover it than to have > developers randomly see the same problem after they happen to purge > their own local. > I totally agree with this one and now that I come think of it, I guess I'm gonna wipe out the CI local repository once a day or once a week. In fact, as a support team, we also would like to be the first informed if the repository is f***d up :). But purging at every build still seems a bit overkill to me, and that's what was being asked here. Cheers. -- Baptiste
