Re: is there a community "best practice" for including your co-workers libraries?

ok, that must be the part I missed. On Mon, Nov 2, 2015 at 7:01 PM, Sean Corfield wrote: > Dave Tenny wrote on Monday, November 2, 2015 at 3:59 PM: > > I'm slightly confused, is there some reason Clojars > doesn't > work for sharing libraries in this context? > > > Because

Re: is there a community "best practice" for including your co-workers libraries?

Dave Tenny wrote on Monday, November 2, 2015 at 3:59 PM: I'm slightly confused, is there some reason Clojars doesn't work for sharing libraries in this context? Because it’s public and sharing your companies libraries with the world might be frowned upon…? Sean -- You received this message

Re: is there a community "best practice" for including your co-workers libraries?

I'm slightly confused, is there some reason Clojars doesn't work for sharing libraries in this context? -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that po

Re: is there a community "best practice" for including your co-workers libraries?

You don't really need to set up a server infrastructure if you can live with hacks. One way is put the JAR say in a "/lib" dir and point the :resource-paths entry in profiles.clj directly to the JAR, so "lib/my-coworker-lib.jar". The other way is http://stackoverflow.com/a/26997656 but I only a

Re: is there a community "best practice" for including your co-workers libraries?

The S3 Wagon is a great option for hosting Maven deps. It takes virtually no maintenance, is backed by AWS, and is dirt simple to configure. It isn't as full featured as some of the other options, but it can't be beat for simplicity. On Sat, Oct 17, 2015 at 4:42 PM Robert Levy wrote: > Many use

Re: is there a community "best practice" for including your co-workers libraries?

Many use s3-wagon or a hosted maven. Or you could install dependencies locally, but that's a pain. On the other hand putting AWS credentials in CI for example to use s3-wagon can be annoying too. What about depending on a specific git remote / commit? This library might be worth giving a shot: ht

Re: is there a community "best practice" for including your co-workers libraries?

We are using Artifactory for our internal Maven repo (supports enterprise Single-Sign-On): https://www.jfrog.com/open-source/ Shantanu On Saturday, 17 October 2015 02:47:29 UTC+5:30, Lawrence Krubner wrote: > > I know this question has been asked before, but when I went searching I > mostly fou

Re: is there a community "best practice" for including your co-workers libraries?

ody, you're not really alive." -- Margaret Atwood From: on behalf of Lawrence Krubner Reply-To: Date: Friday, October 16, 2015 at 2:17 PM To: Clojure Subject: is there a community "best practice" for including your co-workers libraries? I know this question has been asked

Re: is there a community "best practice" for including your co-workers libraries?

I've used Nexus and Archiva, and I feel nexus is a better experience: https://maven.apache.org/repository-management.html There is a stopgap solution involving s3 that might be easier to set up: https://github.com/technomancy/s3-wagon-private On Fri, Oct 16, 2015 at 5:17 PM Lawrence Krubner wrot

is there a community "best practice" for including your co-workers libraries?

I know this question has been asked before, but when I went searching I mostly found old entries that were on a somewhat different topic, such as "How to add a java library (that is not in maven) as a dependency for a clojure library?" I wrote a Clojure app and my co-worker wrote a Java app. I