I'm operating in a medium to large academic environment... maybe 10 to 20 people interacting with a half dozen or more in-house libraries and dozens of projects. All core/common code (currently) is Java: many internal libraries and wrappers for external code. There are numerous projects with only a couple of developers. Some of the projects are used by others, some use some of the others, etc. with varying degrees of interconnected-ness. It's vary likely that while working on my project, for example, I may have to extend a shared library used by many of the others. That library is likely in Java, although, we may start to produce clojure libraries in addition to clojure projects.
Do to the fairly distributed and independent nature of much of the work, an environment where things can live harmoniously would be extremely valuable. (and also allow for clojure to be eased into the system more gracefully without disrupting too much) Phil in your referenced thread, I have numerous situations that are very similar to the example provided by Richard Newman. I'm not sure I fully appreciate or understand the potential symlink solution? Kevin On Apr 14, 2:28 pm, Phil Hagelberg <p...@hagelb.org> wrote: > On Wed, Apr 14, 2010 at 11:46 AM, Kevin Livingston > > <kevinlivingston.pub...@gmail.com> wrote: > > My concern with the Maven and Leiningen approaches for active > > development is that they don't seem to allow for trivial co- > > development of libraries and projects. With ASDF (in Lisp) I could > > say that one project had build dependencies on another, etc. and they > > could happily and trivially be co-developed. In the Maven / Leiningen > > world it seems that each library much be bundled and "published" so > > that projects using them can access it, which seems to cripple the > > fluidity provided by having a REPL and being able to work with > > multiple aspects of your code base at once. > > We have this problem at work with a large multi-module maven build. It > is definitely a very error-prone situation that needs improvement. > > > Is there a best practice that is to be recommended in such an > > environment (multiple java and clojure libraries and projects, > > interconnected, and under co-development)? Anyone else is an > > environment like this? > > It doesn't address the building of Java libraries, but I've recently > added a feature to Leiningen (currently only available in git) that > lets you co-develop several libraries in parallel without going > through an explicit install/fetch-dependencies dance. See this thread > on the Leiningen mailing list for details: > > http://groups.google.com/group/leiningen/browse_thread/thread/f67cb42... > > The feature hasn't seen a lot of use, but it is pretty simple. > > There is a javac plugin for Leiningen, but it's intended for use in > Clojure projects that happen to have one or two .java files that need > compilation (due to annotations or some such), not for building > all-java projects, so this may not cut it for your purposes. But > either way I would love to get more feedback on the approach. > > -Phil -- 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 posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en To unsubscribe, reply using "remove me" as the subject.
