Re: best practice with forked libraries

2015-11-18 15:48 GMT+01:00 Max Gonzih : > I think lein deps :tree should be enough to spot issues like that. > If you're into skimming pages of transitive dependencies (or know how to use grep ;), sure. But lein-collisions also helps you find unexpected collisions (i.e. not

Re: best practice with forked libraries

If you have an internal maven repo, you can publish artifacts to it with updated version string and with group/artifact unchanged. On Wed, Nov 18, 2015 at 7:19 AM Herwig Hochleitner wrote: > 2015-11-18 15:48 GMT+01:00 Max Gonzih : > >> I think lein deps

Re: best practice with forked libraries

I think lein deps :tree should be enough to spot issues like that. Also :exclusions should be used to remove original library from other dependencies. On Wednesday, November 18, 2015 at 3:45:48 PM UTC+1, Herwig Hochleitner wrote: > > 2015-11-17 19:54 GMT+01:00 Ray Miller : >

Re: best practice with forked libraries

2015-11-17 19:54 GMT+01:00 Ray Miller : > > There's a convention in Clojars of deploying a non-canonical fork by > renaming the project to org.clojars.USERNAME/PROJ_NAME and deploying that > to Clojars. > > That convention is pretty awkward in practice, because leiningen and

Re: best practice with forked libraries

Should also work with locally installed jar. On Nov 18, 2015 9:41 PM, "Michael Blume" wrote: > If you have an internal maven repo, you can publish artifacts to it with > updated version string and with group/artifact unchanged. > > On Wed, Nov 18, 2015 at 7:19 AM Herwig

best practice with forked libraries

Say there's a dependency that I fork and add some features I need for my team's project. I can use my fork locally with lein install no problem, and so can others *if* they clone my fork and do the same. It would be more convenient if I could publish my fork to Clojars and depend on that, and

Re: best practice with forked libraries

On 17 November 2015 at 13:21, Bobby Bobble wrote: > Say there's a dependency that I fork and add some features I need for my > team's project. I can use my fork locally with lein install no problem, and > so can others *if* they clone my fork and do the same. It would be more >

Re: best practice with forked libraries

In addition to Ray's response (which I would also suggest), I'd encourage you to reach out to the project maintainer/author with your additions - it's always nice to see how your project is being used and the shortcomings that others are hacking around. Cheers, Paul -- You received this

Re: best practice with forked libraries

A lot of time ago I wrote the following tutorial on this topic. https://github.com/magomimmo/modern-cljs/blob/master/doc/tutorial-19.md HIH mimmo > On 17 Nov 2015, at 20:48, Paul deGrandis