)
> > * Run `:prep-tasks` before `lein test`, so generated test namespaces
> > will be tested. (Martin Reck)
> > * Better error message when attempting to do `lein run` without
> > `project.clj`. (Eduardo Seabra Silva)
> > * Add support for `:managed-depende
The full list of significant user changes:
>>
>> * Add PowerShell script for Windows users. (Brian Lalonde)
>> * Run `:prep-tasks` before `lein test`, so generated test namespaces
>> will be tested. (Martin Reck)
>> * Better error message when attempting to do `lein run` wit
On Monday, June 27, 2016 at 12:45:07 PM UTC-7, Brent Millare wrote:
>
> I'm playing with clojure.spec (alpha7) to validate a data structure
> storing information about workout history using the following code:
>
>
> The problem is that when using s/explain on an invalid input where the
>
We run into this sort of thing quite a bit. Our solution so far has been:
1. Always use `:pedantic? :abort` in the project file. It can be annoying,
but we've found that's much better to get annoying errors about version
conflicts at build time than to get cryptic failures at runtime, such as
Today we did a new release of puppetlabs/trapperkeeper-webserver-jetty9 to
clojars. trapperkeeper-webserver-jetty9 is the main webserver component
for use with our "trapperkeeper" service framework.
The new release is version 1.5.1, and it includes a fix for a memory leak
that would be triggered
Today we released puppetlabs/trapperkeeper v1.3.0 to clojars.
Trapperkeeper[1] is a Clojure framework for hosting long-running
applications and services. You can think of it as a sort of "binder" for
Ring applications and other modular bits of Clojure code.
The major change in the release is
Hi,
As the number of Clojure projects at our company has increased, we've ended
up running into more and more frequent issues where lein's "pedantic" is
alerting us to conflicting versions of transitive dependencies. Up until
now we've been managing this by surgically updating the lists of
Today we did a new release of puppetlabs/trapperkeeper-webserver-jetty9 to
clojars. trapperkeeper-webserver-jetty9 is the main webserver component
for use with our trapperkeeper service framework.
The new release is version 1.4.0, and it includes some initial support for
websockets.
We're
, 1 Jul 2015 at 10:45 Chris Price ch...@puppetlabs.com
javascript: wrote:
Hiya.
We really like the syntax of compojure for defining HTTP routes, but have
had some trouble with use cases where we'd really like to be able to
introspect the route tree, and aren't able to do so because
]:
https://github.com/puppetlabs/comidi/blob/master/project.clj
[discussion]:
https://groups.google.com/forum/#!searchin/clojure/silk$20bidi/clojure/D95anPmhNhU/X7P53cGbfZMJ
On Wednesday, July 1, 2015 at 5:45:40 AM UTC-4, Chris Price wrote:
Hiya.
We really like the syntax of compojure
Howdy. Just wanted to send out some info about a few new services we've
open-sourced for use with our Trapperkeeper service framework recently.
trapperkeeper-metrics:
https://github.com/puppetlabs/trapperkeeper-metrics
This service manages configuration and life cycle of a MetricRegistry (from
Hiya.
We really like the syntax of compojure for defining HTTP routes, but have
had some trouble with use cases where we'd really like to be able to
introspect the route tree, and aren't able to do so because the nested
functions are pretty opaque.
After spending some time trying to workaround
Hi! Just wanted to let everyone know that we recently released a new
version of trapperkeeper-webserver-jetty9 to clojars. The new version is
v1.2.0.
https://clojars.org/puppetlabs/trapperkeeper-webserver-jetty9
It's a feature release; there are a few new config options, but the most
Hi!
We are excited to announce the 1.0.0 release of trapperkeeper and
trapperkeeper-webserver-jetty9. Now that Puppet Labs is shipping several
production apps built on the framework and we consider the API to be
stable, we decided to bump the version number to 1.0.0 and ensure that we
adhere to
We're planning on doing an offiicial 1.0 release of both trapperkeeper[1]
and trapperkeeper-webserver-jetty9[2] in the not-too-distant future, and in
that announcement e-mail we can highlight some of the new features that
have been added over the last few months. However, due to the recent
poodle
that for Trapperkeeper.
Thank you.
Sarwar
On Tuesday, April 15, 2014 4:55:09 PM UTC+1, Chris Price wrote:
Yep, you've pretty much nailed it... the design was heavily inspired by
the OSGi service registry, but we didn't really have a need for most of the
other functionality that OSGi offers. So we
I'm interested! One of the things on the wish list for trapperkeeper is to
make our current configuration service swappable--currently it only
supports files, but I'd really like to be able to swap in a database-backed
config or zookeeper-based implementation. When we get some time to work on
On Wednesday, May 21, 2014 11:14:28 AM UTC-7, mlimotte wrote:
I wrote a ZooKeeper based config system at Climate Corporation. I also
found that there is a need to trigger some action when a config value
changes, and went with a simple callback solution. I do like the idea of
tying this
I have been curious about this too. I was playing around with it a few
weeks ago and came up with this:
https://github.com/cprice404/clj-shared-test-sandbox/blob/master/test/shared_tests_foo/core_test.clj
Which is pretty gross; it uses `binding` + a dynamic var in the shared test
namespace,
Recently a few co-workers and I have been discussing options related to
compiling a few tiny Java libraries that some of our Clojure libraries
depend on. We realized that we should be explicitly setting the Java
source/target version for jars that we publish to clojars/maven central.
Now we're
-survey/
On Monday, April 28, 2014 12:56:51 PM UTC-5, Chris Price wrote:
Recently a few co-workers and I have been discussing options related to
compiling a few tiny Java libraries that some of our Clojure libraries
depend on. We realized that we should be explicitly setting the Java
Yep, you've pretty much nailed it... the design was heavily inspired by the
OSGi service registry, but we didn't really have a need for most of the
other functionality that OSGi offers. So we basically just came up with a
way to describe services via Clojure protocols, and then we wire them
We published a follow-up post this morning, with a lot more detail on the
Clojure side of things:
https://puppetlabs.com/blog/clojure-nerds-puppet-labs-application-services
On Sunday, April 13, 2014 6:48:10 PM UTC-7, Walter Heck wrote:
As a non-clojure user, but a Puppet expert (ahum ;) ) I
23 matches
Mail list logo
