Inhouse repo, if you look at Proximity is very important to achieve stable and controlled build environment.
If you have some company level (reaches through more separate projects) some-utility.jar, how will you spread it amongst developers? How will you achieve if some-utility.jar is updated, to update all developer environment too? Will everybody issue "maven install:install-file"? They could :) Publish it on the inhouse repo and done. Every developer will acess your artifact as they access for example log4j. See here https://is-micro.myip.hu/projects/ismicro-commons/proximity/ ~t~ On 5/26/06, Kathryn Huxtable <[EMAIL PROTECTED]> wrote:
Of course, one answer leads to another question... ;-) Why bother proxying inhouse repositories? I don't see the logic there. -K
