On 1 July 2010 17:49, Kevin Livingston <kevinlivingston.pub...@gmail.com> wrote: > Some of the build tools like Maven can help a lot. > > However, one different/related issue I have is when I have multiple > projects I am developing, say a library, LibA, and a project that uses > it ProjB, if I want to co-develop them, it can get a little hairy, and > I haven't figured out the solution... > > since in the java-only world maven would (i think, I'm still a little > new to it) see LibA as a dependency to ProjB, compile it, jar it, and > put the jar on ProjB's class path. That's great in the java world > where you (almost) always run fresh instances. But in a Lisp with a > REPL you'd want to change something and reload just that piece. So > I'd like to edit LibA stuff and reload it in the ProjB (already > running) REPL but it seems like the classpath will be out of whack for > this. using something like swank through clojure-maven.
If you have a directory containing Clojure a source code tree for LibA on the classpath for ProjB then you should be able to replace the files without changing any classpath. > presumably people co-developing clojure-contrib and clojure core have > this same issue? > it looks like clojure is brought into the clojure-contrib as a system > dependency under a build profile... seems do-able for my problem, are > there pro's and con's to any alternatives? -- Michael Wood <esiot...@gmail.com> -- 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
