Merge pull request #34 from kbaribeau/master

Upgrade to latest Grunt
remove grunt-contrib-connect, since we're already
using express for lineman's development server
Fixed two problems that emerged on `lineman new`

- I got too aggressive in killing __dirname's
- The templating in the archetype's package.json
was using invalid identifiers (they were trying to
subtract contrib from grunt, which was a bit fun)
blindly converts everything but cli.js to 
coffeescript. seems to work, but:

1. watch fails to render new generated js. 
was this a problem introduced by 
grunt 0.4 or by switching to express??

2. cli.js will need to have its logic pulled out
into a new file if it's going to be in coffee as
well.
watch configuration appears to now require arrays
for task definition (this is generally becoming
a theme throughout grunt, which is trying to 
add support for spaces in task args)
when lineman is called and no command matches,
it will try calling grunt with those commands
as if it was given an arbitrary task name.

This wasn't added for funsies, because the 
watch task changed how it spawns grunt in such a
way that it will inadvertently spawn lineman on
a watch match. As a result it seemed easiest to just
quack like grunt.

HOWEVER this seems to be significantly slower from
the user's experience. which is totally not cool.
Merge pull request #35 from testdouble/coffee

the coffeescript PR
dont use urlencoded() middleware

bodyParser does these three things:

app.use(express.json());
app.use(express.urlencoded());
app.use(express.multipart());

I haven't tracked down the *exact* cause, but I'm pretty close. In any
case the urlencoded() middleware breaks POSTs going through the proxy.

See https://github.com/kbaribeau/node-proxy-timeout-test