Mark Derricutt

On 7 May 2014, at 6:43, Kevin Livingston wrote: > This seems to happen regardless of clojure-maven-plugin -- the project > I was depending on when I was modulating that...

On 27 Jun 2014, at 11:59, Kevin Livingston wrote: > Comparing my projects to the documentation I notice that my projects > are package type `jar` does that matter? Nope...

Re-reading this. This is standard maven dependency behaviour. Just having a version of "0.1.0" and means "I would like 0.1.0, but if anyone else wants something higher - use it"....

Maybe we should make the creation of the jar a configuration setting, that when running on windows defaults to true ( where this was intended to solve an issue )...

...and then the Java classes won't be able to refer to the clojure. Catch22. If you add a `` declaration for the `maven-compiler-plugin` _after_ the `clojure-maven-plugin` it should, in theory...

Hey there, Hrm - it should be doing this already when it doesn't detect/discover any namespaces to compile, or do you have a setup with mixed java/clojure code? What triggers...

Hi - what version of the plugin are you using? the clojure packaging style only came in with 1.3.4. Also, if using the clojure packaging style, you need true in...

It could still be worth adding actually - as just calling `coffee` gives you zero guarantee over a) the version of coffee your using b) the version of node that...

What configuration are you actually using? We use: ``` src/main/coffee target/javascript-src ``` using `1.4.16` and each `.coffee` file is compiled fine to individual `.js` files.....

Hi there - started to take a look at this - good stuff! I've been meaning to implement something like this for awhile to speed up our own builds. One...