First beta of Ring 1.1.0

[James Reeves]

The first beta of Ring 1.1.0 is now on Clojars. There's nothing
revolutionary in this release, but there are a number of minor
improvements, including:

- Support for SSL client certificates
- Updated Jetty version to 7.6.1
- Functions in ring.util.io for turning OutputStreams into InputStreams
- Support for clj-time in wrap-cookie expiry
- Functions for encoding form data in ring.util.codec
- Small middleware, wrap-head, for handling HEAD requests

In addition, ring-devel now depends on Hiccup 1.0, so you can use the
new Hiccup version without conflicts.

You can use the Ring beta by adding the following dependency:

[ring "1.1.0-beta1"]

I'll come up with a more detailed description of the changes and Codox
API docs before the final release date. At this point, we're basically
feature-complete; there's just a bit of housework left to do.

- James

[Bruce Durling]

Excellent news. Time to update all my websites now... ;-)

cheers,
Bruce

--
CTO & co-founder
@MastodonC
mastodonc.com

[Bill Caputo]

Hi Ring group,

Does ring push snapshots to clojars? If not, is there a recommended way to depend on the latest version of master? Specifically: We want to pick up the change represented by pull request #65 and I'm not sure how best to go about doing that. Right now, we're working off a local build of our fork, which I'd rather not move to our production environment as it'll require setting up a local repository or pushing the fork to clojars... (or something else?)

Another alternative is to just wait for the change to make it to clojars via a beta-2 or 1.1.1 push, but unless that's happening in the next couple of days, I'll need to go with one of the others...

thanks,
bill

[James Reeves]

On 26 March 2012 21:29, Bill Caputo <logo...@gmail.com> wrote:
> Does ring push snapshots to clojars?

Not on each commit, but I can push out a 1.1.0-beta2 if you want it.

- James

[James Reeves]

There's now a 1.1.0-beta2 on Clojars with the changes you want.

- James

[Bill Caputo]

Awesome, thanks James.. that solves our problem... on a more general note, is there a reason not push on each commit (i.e. is that common or uncommon in clojure-land?, frowned upon by clojures, etc) seems like a reasonable idea otherwise...

bill

[Shantanu Kumar]

On Mar 27, 2:35 am, Bill Caputo <logos...@gmail.com> wrote:
> Awesome, thanks James.. that solves our problem... on a more general note, is there a reason not push on each commit (i.e. is that common or uncommon in clojure-land?, frowned upon by clojures, etc) seems like a reasonable idea otherwise...

I guess you can do so on your own:

$ cd /pathto/repos/ring
$ git pull
$ lein2 install
$ lein2 sub install

This will install the latest version to your local repo that you can
use from your project.

Shantanu

[Bill Caputo]

On Mar 27, 2012, at 1:47 PM, Shantanu Kumar wrote:
[snip install example]

>
> This will install the latest version to your local repo that you can
> use from your project.

Yup, we already do that for development (well we use the leiningen 1.x plugin localrepo) - and is how we tested against the fork - but that doesn't scale across multiple projects/code bases/servers/workstations/etc very well. (hence the desire to get a push of beta-2). My question was just curious what was "policy"...

bill