Hey Christopher, That clarifies things.
Many thanks, Mark On 25 January 2012 16:15, Christopher Tiwald <ctiw...@salsalabs.com> wrote: > On Jan 25, 2012, at 9:57 AM, Christopher Tiwald wrote: > > The reason why I'm trying to avoid a public repository is because the > application needs to compile inside a client's network and they have a > network policy which only allows port 80. I am (perhaps incorrectly) > assuming that connections to pubilc repositories go through some port other > than 80 though. Is my assumption correct? > > > Uhhh. I think so? Looks like the API at search.maven.org would let you do > jar downloads over HTTP. > > > Whoops. Meant to suggest I think they are run off port 80. Regardless, you > should be able to test it with that buildfile, using whichever public > repositories you choose. You could also consider setting up a local > artifactory installation inside their firewall: > http://www.jfrog.com/products.php. It's straightforward to setup and easy > to maintain. > > All the same, if remotes aren't right for your use case, stick with the > lib/* directory. Remote public repos carry some strong advantages, but it > might not be worth the extra work :-). Their source shouldn't have any > significant impact on your ability to compile or package your application > in buildr. > > -- > Christopher Tiwald > > Reliability Architect > Salsa Labs, Inc. > -- --- Mark Coleman - +31(0)652134960 - Mixtup <http://www.mixtup.nl> [image: Facebook]<http://www.facebook.com/pages/The-Mixtup-Project/161049465955>[image: Youtube] <http://www.youtube.com/user/MixTupMovies>[image: Vimeo]<http://vimeo.com/user4061445/videos>
