I'm away until Thursday, and will probably be more available next week. I would love to squeeze a release this month so adding clojure support is not at the top of my list at this point, but I can try to work on it if we are ahead of the curve.
Thanks, Antoine On Sun, Aug 8, 2010 at 20:47, Alex Boisvert <[email protected]> wrote: > Thanks Chris. I'm traveling this week and on semi-vacation so I'll > take a look when I return. > (Other committers are welcome to review and commit.) > > alex > > On Friday, August 6, 2010, Chris Dean <[email protected]> wrote: > > I added a patch to https://issues.apache.org/jira/browse/BUILDR-259 > > > > There is also a git repo at http://github.com/ctdean/buildr > > > > Cheers, > > Chris Dean > > > > Alex Boisvert <[email protected]> writes: > >> The best way to send a patch is through Jira (and clicking the ASF > license > >> grant checkbox). > >> > >> *BUT* if you think the code needs some iterating over (by you or other > >> non-committers) before it's finalized, it's probably better to put it on > >> github as a fork of http://github.com/apache/buildr. > >> > >> Another option would be to keep it separate from buildr and package it > as a > >> plugin (gem). This way, it could evolve independently of buildr on its > own > >> release cycle. If you're interested in trying this out but getting it > to > >> work as a plugin seems like a challenge to you, let's start with a > complete > >> fork and I can help to make it a plugin as a second step. > >> > >> alex > >> > >> > >> On Thu, Aug 5, 2010 at 2:12 PM, Chris Dean <[email protected]> wrote: > >> > >>> I have something working on my desktop. I'm sure that there are many > >>> things wrong, but it's ready for someone else to take a look at it. > >>> What's the best way to send a patch? > >>> > >>> Currently we have working: > >>> > >>> - Compiling clojure > >>> - Running clojure tests > >>> - A clojure shell/repl > >>> - A running swank server (Swank is part of an Emacs dev environment) > >>> - Some docs > >>> > >>> for some definition of "working". > >>> > >>> Cheers, > >>> Chris Dean > >>> > >>> Chris Dean <[email protected]> writes: > >>> > Thanks. I'll give it a go. > >>> > > >>> > My ignorance of Buildr is profound, but I'll see if I can stumble > >>> > through. > >>> > > >>> > Cheers, > >>> > Chris Dean > >>> > > >>> > Daniel Spiewak <[email protected]> writes: > >>> >> Tweak the branch! Tweak the branch! :-) > >>> >> > >>> >> It is quite a bit out of date, I must admit. I think I had it > updated > >>> to > >>> >> Buildr 1.3.5 and Clojure 1.0, but that was about where things > stopped. > >>> >> Clearly things have moved forward since then. My advice to you > would be > >>> to > >>> >> fork that branch and then rebase it forward to the latest from > git:// > >>> >> git.apache.org/buildr.git (which is an official mirror of the SVN, > >>> >> maintained by Apache). If you can get something working, we would > love > >>> to > >>> >> fold it into the Buildr mainline. I've always thought that Clojure > >>> support > >>> >> in Buildr would be cool (naturally, since I started the branch), I > just > >>> >> haven't had time to work on it recently. > >>> >> > >>> >> Daniel > >>> >> > >>> >> On Thu, Jul 8, 2010 at 9:59 PM, Chris Dean <[email protected]> > wrote: > >>> >> > >>> >>> I'm interested in using Buildr on a Clojure project. I downloaded > a > >>> >>> fork of buildr from http://github.com/djspiewak/buildr and managed > to > >>> >>> get that somewhat working. > >>> >>> > >>> >>> If I wanted to continue using Buildr and Clojure what is the best > path > >>> >>> to take? Should I tweak this branch? or is there something working > in > >>> a > >>> >>> newer branch? > >>> >>> > >>> >>> Thanks! > >>> >>> > >>> >>> Cheers, > >>> >>> Chris Dean > >>> >>> > >>> > > >
