Gotcha! Thanks!

On Friday, November 7, 2014 4:22:35 PM UTC+1, Micha Niskin wrote:
>
> Henrik, the -d option simply adds dependencies to the project. The main 
> use case for this option is to pull in dependencies when you have no formal 
> “project” and no build.boot file. Mainly it’s used in concert with the 
> repl task so you can quickly and easily try something out:
>
> $ boot -d aysylu/loom repl
>
> boot.user=> (use 'loom.graph)
> nil
> boot.user=> (graph [1 2] [2 3] {3 [4] 5 [6 7]} 7 8 9)
> ...
>
> However, if a dependency pulled in via -d (not transitive deps) contains 
> namespaces in which tasks are defined, these namespaces may be tagged with 
> ^:boot/export-tasks metadata. Boot will find these namespaces and refer 
> all public vars into your build.boot environment.
>
> So if the reagent jar contained task namespaces you should see them when 
> you do
>
> $ boot -d reagent
>
> Note that you don’t need to supply the group-id for reagent, and if you 
> want the latest release you can also omit the version.
> ​
>
> --
> Micha Niskin
>
> On Fri, Nov 7, 2014 at 4:16 AM, Henrik Eneroth <henrik....@gmail.com 
> <javascript:>> wrote:
>
>> I tried now, just running boot -u, and it worked perfectly. It's was 
>> probably some caching thing with Clojars. Currently at pre21
>>
>> Now the command runs without errors, but it also doesn't seem to do all 
>> that much.
>>
>> Running 
>> > boot -d reagent/reagent:0.4.3
>> gives the exact same output as running 
>> > boot -h
>> currently.
>>
>>
>>
>> On Friday, November 7, 2014 12:18:41 AM UTC+1, Micha Niskin wrote:
>>>
>>> It looks like Clojars is doing what I thought it would do: 
>>> https://clojars.org/repo/boot/boot/maven-metadata.xml
>>>
>>> <release>2.0.0-pre20</release>
>>>
>>> On Thursday, November 6, 2014 5:50:14 PM UTC-5, Henrik Eneroth wrote:
>>>
>>> Thanks for looking into it, Micha! 
>>>>
>>>>
>>>> I'm getting -pre19 with boot -u, though. Did you forget to cut a 
>>>> release or should I set BOOT_CHANNEL to dev?
>>>>
>>>>
>>>> On Thursday, November 6, 2014 8:30:55 PM UTC+1, Micha Niskin wrote:
>>>>>
>>>>> Hi Henrik,
>>>>>
>>>>> You found a bug! We just fixed it though. Boot was confused by 
>>>>> `reagent/reagent` when it tried to match that against the artifact ids 
>>>>> returned by Pomegranate, because Pomegranate collapses it to just 
>>>>> `reagent` 
>>>>> in that case. If you do `boot -u` you should be updated to boot version 
>>>>> `2.0.0-pre20`, and your command line will work.
>>>>>
>>>>> On Thursday, November 6, 2014 12:31:13 PM UTC-5, Henrik Eneroth wrote:
>>>>>>
>>>>>> Hello Micha!
>>>>>>
>>>>>>
>>>>>> I'm trying to tuck Reagent in there to take it for a spin, and it 
>>>>>> seems reluctant to comply:
>>>>>>
>>>>>> boot -d reagent/reagent:0.4.3
>>>>>> java.lang.NullPointerException:
>>>>>>              boot.main/dep-ns-decls  main.clj:   36
>>>>>> boot.main/export-task-namespaces/fn  main.clj:   49
>>>>>>                 clojure.core/map/fn  core.clj: 2557
>>>>>>                                 ...
>>>>>>                    clojure.core/seq  core.clj:  133
>>>>>>                  clojure.core/apply  core.clj:  624
>>>>>>                 clojure.core/mapcat  core.clj: 2586
>>>>>>                                 ...
>>>>>>    boot.main/export-task-namespaces  main.clj:   51
>>>>>>                     boot.main/-main  main.clj:  111
>>>>>>                                 ...
>>>>>>                    boot.App.runBoot  App.java:  217
>>>>>>                       boot.App.main  App.java:  309
>>>>>>
>>>>>>
>>>>>> Any feedback on what I (or it) may be doing wrong?
>>>>>>
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> Henrik
>>>>>>
>>>>>> On Monday, November 3, 2014 9:40:58 PM UTC+1, Micha Niskin wrote:
>>>>>>>
>>>>>>> Hi!
>>>>>>>
>>>>>>> Boot (http://github.com/boot-clj/boot) is a build tool for Clojure. 
>>>>>>> We've pulled together lessons learned from a year or so using boot v1 
>>>>>>> in 
>>>>>>> production and are now getting ready to release v2. To show what boot 
>>>>>>> can 
>>>>>>> do we present a very streamlined and awesome boot-based ClojureScript 
>>>>>>> development workflow (http://adzerk.com/blog/2014/
>>>>>>> 11/clojurescript-builds-rebooted/). 
>>>>>>>
>>>>>>> Try it out, maybe you'll like it! We're hoping to get some feedback 
>>>>>>> before committing to a stable release, so please if you have any 
>>>>>>> comments 
>>>>>>> or questions we'd be happy to hear them. Have fun!
>>>>>>>
>>>>>> ​
>>>
>>  -- 
>> You received this message because you are subscribed to the Google
>> Groups "Clojure" group.
>> To post to this group, send email to clo...@googlegroups.com 
>> <javascript:>
>> Note that posts from new members are moderated - please be patient with 
>> your first post.
>> To unsubscribe from this group, send email to
>> clojure+u...@googlegroups.com <javascript:>
>> For more options, visit this group at
>> http://groups.google.com/group/clojure?hl=en
>> --- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Clojure" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/clojure/YAckwMSfZkY/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> clojure+u...@googlegroups.com <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to