just be aware of the fact that this plugin does not take into account plugins.
mimmo
On Mar 6, 2013, at 1:06 PM, Tom Hall wrote:
> Now that's just what I need, thanks David
>
> On 5 March 2013 15:42, David Powell wrote:
>> You could try the lein-outdated plugin.
>>
>> https://github.com/ato/l
Now that's just what I need, thanks David
On 5 March 2013 15:42, David Powell wrote:
> You could try the lein-outdated plugin.
>
> https://github.com/ato/lein-outdated
>
> It looks at your project.clj, and tells you if there are newer versions of
> any of your dependencies, and if so, what they
You could try the lein-outdated plugin.
https://github.com/ato/lein-outdated
It looks at your project.clj, and tells you if there are newer versions of
any of your dependencies, and if so, what they are.
Eg:
lein outdated
[org.clojure/clojurescript "0.0-1586"] is available but we use "0.
$ lein search clojurescript
Searching over Artifact ID...
== Showing page 1 / 2
[org.clojure/clojurescript "0.0-927"] ClojureScript compiler and core
runtime library.
(...)
[org.clojure/clojurescript "0.0-1576"] ClojureScript compiler and core
runtime library.
[org.clojure/clojurescript "0.0-1586"
Simplest way is to either search for org.clojure/clojurescript in Central:
http://search.maven.org/#search%7Cga%7C1%7Corg.clojure%2Fclojurescript
or check the name of the latest tag in the repo:
https://github.com/clojure/clojurescript/tags
(the version string is 0.0-N for tag rN).
Also, lein-
> Sure, just add it as an explicit dependency to your project. In fact,
> your example uses r1450 only because you've got an explicit dependency
> on it, as lein-cljsbuild 0.3.0 uses r1552 by default, so you could
> also drop the explicit dependency. It's best to use the latest release
> though.
C
On 5 March 2013 11:24, Tom Hall wrote:
> Thanks Michał, is it easy enough to start using later versions of cljs
> with lein-cljsbuild?
Sure, just add it as an explicit dependency to your project. In fact,
your example uses r1450 only because you've got an explicit dependency
on it, as lein-cljsbu
On Mar 5, 2013, at 11:24 AM, Tom Hall wrote:
> Thanks Michał, is it easy enough to start using later versions of cljs
> with lein-cljsbuild?
Hi Tom,
you can eventually take a look at https://github.com/magomimmo/modern-cljs to
see if it can help you in starting with lein-cljsbuild plugin, which
Thanks Michał, is it easy enough to start using later versions of cljs
with lein-cljsbuild?
On 5 March 2013 00:16, Michał Marczyk wrote:
> PS. Incidentally, cljs-1450 has a bug which causes it to emit the
> unmunged property name regardless of the filenames used. The relevant
> ticket is CLJS-336
PS. Incidentally, cljs-1450 has a bug which causes it to emit the
unmunged property name regardless of the filenames used. The relevant
ticket is CLJS-336, fixed in 9824dbd7c8ac658ebc2d5bc9fa6b5b898f17f659
(releases >= 1503).
On 5 March 2013 01:06, Michał Marczyk wrote:
> This particular problem
This particular problem goes away if you use ClojureScript release
1586 *and* rename the directory
src/cljs/aima-clojure
to
src/cljs/aima_clojure
and the file
tictactoe-frontend.cljs
to
tictactoe_frontend.cljs
Maybe we should warn on encountering filenames with dashes, or else
treat
Hello,
I have just been stuck for ages trying to figure out what was going on
in my first clojurescript application and think I have found a bug.
I took some working game playing code for a simple tictactoe example
and found that I got incorrectly names JS outputted
I have created a project with
12 matches
Mail list logo
