Re: logback.xml being picked up twice in project (how do I surpess the inheritted projects logback.xml)?

2013/8/16 Stephen Cagle : > Sorry if I am being dense, just want to make sure I understand what you are > saying... > > So, I was including logback.xml in my git source control. I take it you > would say that is a bad idea? I thought it made sense as I then have it as > part of the project, but I s

core.async - handling nils

Hi all, I'm experimenting with core.async. Most of it is exceptionally good, but bit I'm finding it *very* inconvenient that nil can't be sent over channels. In particular, you can't pipe arbitrary Clojure sequences through channels (since sequences can contain nils). I see this as a pretty b

Re: logback.xml being picked up twice in project (how do I surpess the inheritted projects logback.xml)?

Sorry if I am being dense, just want to make sure I understand what you are saying... So, I was including logback.xml in my git source control. I take it you would say that is a bad idea? I thought it made sense as I then have it as part of the project, but I suppose it could get in the way in

Re: logback.xml being picked up twice in project (how do I surpess the inheritted projects logback.xml)?

The trick is, don't build the original jar with the logback config file. No dependent of that jar wants to be told how to do logging. You should keep your logback.xml in the /config directory, not in /resources. As far as -D, that's to pass environment parameters to the JVM. See http://logback.qos

Re: logback.xml being picked up twice in project (how do I surpess the inheritted projects logback.xml)?

I don't know what -D is, other than a one eyed laughing face. :D Is there some sort of standard for this? Do people simply write a script that checks out the code and remove files that they don't want in the generated jar? Is there something I can put in my project.clj that specifies what I *do

Re: logback.xml being picked up twice in project (how do I surpess the inheritted projects logback.xml)?

You shouldn't include the logback.xml in the generated jar file. Only the ultimately generated artifact should have a logback.xml file, best loaded from the file system (possibly through -D). It doesn't matter what settings base has for logging, derive should set all logging parameters. jason

logback.xml being picked up twice in project (how do I surpess the inheritted projects logback.xml)?

I have project 'base' that has a logback.xml file and project 'derive' that also has a logback.xml file. Project 'derive' has a dependency on 'base'. When I "lein trampoline repl" on project 'derive', I get the following warning. 15:34:30,066 |-INFO in ch.qos.logback.classic.LoggerContext[

ANN 2 day Clojure workshop in Munich, Germany

I'm happy to announce a 2 day Clojure workshop in Munich, Germany on Oct 12-13, 2013. It is taught by production Clojure users (SoundCloud, StyleFruits engineers) and 1 ClojureWerkz team member. No prior Clojure experience is required but experience with at least one programming language is necess

Re: Storing Clojure code in a data store

How is quicklisp different that clojars + leiningen? On Thursday, August 15, 2013 8:41:16 AM UTC-7, da...@axiom-developer.org wrote: > > It might be useful to set up a website similar to quicklisp for clojure. > I've found quicklisp to be very effective as it not only delivers code > but resolv

Re: Storing Clojure code in a data store

Hi Luc, Thanks for sharing, good to know someone is doing this. We're using Avout / ZK and are looking at Riac so this could be an option. Jon. -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googleg

Re: Storing Clojure code in a data store

It might be useful to set up a website similar to quicklisp for clojure. I've found quicklisp to be very effective as it not only delivers code but resolves dependencies to other packages automatically. Tim Daly -- -- You received this message because you are subscribed to the Google Groups "Cl

Re: Storing Clojure code in a data store

We store code/data in zookeeper and riak. We serialize these using nippy. You can get notified on changes using zookeeper watchers on the nodes storing either children changes or changes to the node data as you wish. We are highly satisfied with this, we also store configuration data in zookeeper

Storing Clojure code in a data store

Hi, I'm wondering what approaches people take if they want to have Clojure code loaded at runtime from some data store. We operate a large website and I'd like the ability to deploy our mustache templates & immediate corresponding clojure code at will, rolling back etc if need be, without having

Re: [ANN] bouncer 0.2.4-alpha1 [breaking changes]

and of course by prefix I meant suffix! Ok. Time for bed. Leonardo Borges www.leonardoborges.com On Fri, Aug 16, 2013 at 12:41 AM, Leonardo Borges < leonardoborges...@gmail.com> wrote: > Sold. > > I've released it as "0.3.0-alpha1". I kept the alpha prefix as I'm the > only one using this vers

Re: [ANN] bouncer 0.2.4-alpha1 [breaking changes]

Sold. I've released it as "0.3.0-alpha1". I kept the alpha prefix as I'm the only one using this version now. Will release the final package after a few people have used it. Please do not use "0.2.4-alpha1" - I opened a ticket [1] with clojars to delete that version. [1]: https://github.com/ato/

Re: [ANN] Marginalia has a new home

This is my first major contribution to the Clojure community so I'm looking forward to continuing the great work that Fogus et al have done. I'd like to publicly thank Fogus for letting me take the reins on a major project as a learning experience. It's another example of why the Clojure com

Re: [ANN] bouncer 0.2.4-alpha1 [breaking changes]

I like releasing it as 0.3.0. --- Joseph Smith j...@uwcreations.com @solussd On Aug 15, 2013, at 9:20 AM, Leonardo Borges wrote: > Hi Moritz, > > Thanks for the suggestion. You're right and I missed this. > > I'll make sure I take this into account for the next release - I could > rele

Re: [ANN] bouncer 0.2.4-alpha1 [breaking changes]

Hi Moritz, Thanks for the suggestion. You're right and I missed this. I'll make sure I take this into account for the next release - I could release it as 0.3.0-alpha1 but then I'd like to remove 0.2.4-alpha1 from Clojars which doesn't seem to be a trivial thing to do. Leonardo Borges www.leon

Re: [ANN] bouncer 0.2.4-alpha1 [breaking changes]

Just a small suggestion: Bugfix releases (z in x.y.z) are usually considered to be non-breaking, so breaking changes in such releases might cost people time when they assume they can upgrade without changing their code. It's nicer to introduce breaking changes to minor- or major-releases (x or y

[ANN] bouncer 0.2.4-alpha1 [breaking changes]

Hi all, bouncer is a validation library for Clojure apps Github: https://github.com/leonardoborges/bouncer Clojars: https://clojars.org/bouncer Version 0.2.4-alpha1 has undergone major, breaking changes: - My original design made heavy use of macros for a nicer, more natural DSL at the expense

ANN swag a DSL for documenting Compojure routes using Swagger

Swagger is a cool project for documenting Restful API's, Swag is a DSL that wraps Compojure routes enabling them to be listed and described automagically without the need of maintaining json https://github.com/narkisr/swag Feedback is welcome Rone

Re: function creation, partial or #()

> (let [params (map (fn [_] (gensym "fnp-")) (range n))] > (repeatedly n #(gensym "fnp-")) Best, Stefan -- -- 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