-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks,
So I'm in a bit of a conundrum, and would like some ideas. Most of the time I work with my laptop connected to an internal network, with its own maven repository (Nexus OSS). I proxy all external repositories through this and everything works fine. Sometimes though, I'm out and about and need to do some work. From other discussions on the mailing list, I understand that there are two approaches: 1. work offline 2. set up an additional maven repository proxy on the laptop I've done the second, but I'm a little confused as to how to optimally configure both the proxy and settings.xml. Currently, I have everything in settings.xml on the laptop pointing to the laptop's repository. I then have the laptop's repository pointing to the internal network repository. This works fine while I'm connected to the internal network, but will fail to resolve artifacts if I'm not connected to the internal network and have not previously resolved the artifact. This behavior is exactly like not running a proxy repository on the laptop. Another configuration would be set up the laptop repository to proxy internal repositories (I have 4), but point directly to the internet repositories for Maven Central and a few others I use. This will work whether I'm connected to the internal network or not, but will have three drawbacks. 1. The internal repository will not be populated with artifacts I pull down from central while disconnected 2. This doesn't scale well - if there are 100s of mobile developers, this sends unnecessary traffic to central 3. The internal proxy will not have a collection of central artifacts Item 1 is unavoidable. Items 2 and 3 are not so nice. I guess the third solution would be as follows (using Nexus OSS as an example). 1. use one set of proxy definitions while connected internally a. point to the internal proxy b. this proxies internal-only repositories c. this proxies central and other internet-connected repositories 2. use another set of proxy definitions when mobile a. activate direct connection to central (and others) when mobile b. deactivate proxy connection to central (and others) when mobile Would the third solution be viable (except for the fact that there's a lot of fiddling involved)? Pointers, advice, and thoughts greatly appreciated. . . . . 'twas the night before Christmas, and Maven abounds /mde/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJUm6p8AAoJEEFGbsYNeTwtB6wIAKtgi8w9J7YUGzLPcuYBF6EU kRcNUy+nfbfqDLhMY9MU9YuW/1M5MtwjYaEpDxgZKSUz75K1YEkAnGU68Y/JhtQR WNk4XoHMeZmtp5ggTgJR8lLZHQqigedGy8ZvvQJQt+W4eTO4EF/CnWsh4vCIGnBF Bj+jmFnvwm210hRoJmrUVezv8+zZxMxULCAUGDKX7gNOVLl+aKQvnZSOo8icSbX0 zrWyns+dtcMc/qC5iujW9n2WaSRLpwZFB6fiK5SPr+ZbOJTaeNh+f7GYYDSfZ5/x 9Gq2leMG79zQkz3Zg9BVdX+yo8hPQFvSSLq6POQfJDT4gJ2gp0My0h0qlK5tgNk= =2bNJ -----END PGP SIGNATURE----- --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
