On Fri, Jun 26, 2009 at 5:51 PM, Raymond Feng<[email protected]> wrote: > Reliable means: > > 1) It can be trusted
That's a fair point. If you have a reason not to trust a repository to carry the artifacts as the author intended. > 2) Its downtime should be very low and the performance should be reasonable > 3) It will be available forever:-) (when we have released artifacts that > reference the repo, we create a hard dependency for the maven build on it) "forever" seems a bit of a tall order. If we have problems with a repo then we have quite a few other repos in the build that could take over. Even if that means copying artifacts to our repo at a later date. I'm just nervous of setting the expectation that we will maintain a repo. We have no choice if an artifact is available nowhere else. But if it is then I think we should consider that before going ahead and copying it. > > If an artifact is not available in the maven central or any reliable > alternatives such as java.net, I prefer to have own control like other > Apache projects do (Geronimo, ServiceMix, Axis2 etc). >
