Too right.

Yes, wrt the multi-project / classpath thing, running isolated test for a
particular project is only one aspect. I also have an eye to running a i)
browser-connected repl and ii) debugger for a particular project. So those
things, along with iii) running tests, make very high, the attractiveness
of having that isolation.

I'll try to put those in github issues. And also pick at the problem myself
when I get some cycles. I think it would add a powerful feature to the
tool. Anyways... :)


Tim Washington
Interruptsoftware.ca <http://interruptsoftware.ca/> /
Bkeeping.com<http://bkeeping.com/>



On Tue, Nov 5, 2013 at 4:33 AM, Malcolm Sparks <malc...@juxt.pro> wrote:

> Hi Tim,
>
> The tests in JUXT accounting are using clojure.core.test. I'm fairly sure
> Midje's :autotest feature does something dynamic to determine the tests to
> run and that may not work with Jig's classloading approach. For example, if
> something uses (System/getProperty "java.class.path") it will just get the
> Jig source directories because, for external projects, Jig must load these
> using a child class-loader. I need to spend some time with Midje to work
> out what it's doing.
>
> Having multiple lein projects loaded in the same JVM, and integrated with
> each other, is not a common Clojure mode of usage today. However, the
> Immutant team (and others) have done a lot of the groundwork and I think
> the various caveats I've listed on Jig's README.md about 'external
> projects' are going to be ironed out over time as these issues become
> better understood. I expect that Brian never saw this as a use-case.
>
> In the absence of a mailing list right now, please log any issues you see
> as GitHub issues and I'll do my best to fix them.
>
> Thanks again for sending in this really useful feedback.
>
> Regards,
>
> Malcolm
>
>
>
>
> On Monday, 4 November 2013 02:53:47 UTC, frye wrote:
>
>> Ok, some more feedback for Jig.
>>
>> *A)* Testing - Let's say I have a multi-project jig, with dependencies
>> across projects. There doesn't seem to be a way to run tests (midje
>> :autotest) for a specific project. I tried creating a Midje component (see
>> https://www.refheap.com/20442). But when I *i)* put this into
>> config.edn, and *ii)* thread through my local project component, *iii)*this 
>> only prints out the classpath directories under the
>> *jig* project. I'll want to be in the Classpath context of the project
>> that's being passed in. That way, I can :autotest for that project. Or
>> perhaps there's another way to run and autorun tests for a particular
>> project. I noticed that 
>> Juxt-Accounting<https://github.com/juxt/juxt-accounting>has a test suite.
>>
>> *B)* Ok, so there's just that and removing the *config/console.edn* and
>> *config/default.edn* files when writing your jig.
>>
>> *C)* And a raw *git clone g...@github.com:juxt/jig.git*, then *lein repl*,
>> then * (go)*, doesn't give working URLs ( http://<>:8091/readme , 
>> http://<>:8001/server,
>> etc )
>>
>>
>> Let me know if you want me to log these as bugs, feature requests, etc.
>> Very excited about the kind of leverage that this project can yield.
>>
>>
>> Loving this tool. Thanks.
>>
>> Tim Washington
>> Interruptsoftware.ca <http://interruptsoftware.ca/> / 
>> Bkeeping.com<http://bkeeping.com/>
>>
>>
>>
>> On Sat, Nov 2, 2013 at 8:18 PM, Timothy Washington <twas...@gmail.com>wrote:
>>
>>> Ok, I actually got the compojure example working. I just had to remove
>>> the *config/console.edn* and *config/default.edn* files in my jig. They
>>> must be disrupting the config that I put in. So that's my only feedback so
>>> far.
>>>
>>> Ok, this is looking really good. Great work :)
>>>
>>> Tim Washington
>>> Interruptsoftware.ca <http://interruptsoftware.ca/> / 
>>> Bkeeping.com<http://bkeeping.com/>
>>>
>>>
>>>
>>>
>>>  --
> --
> 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/groups/opt_out.
>

-- 
-- 
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/groups/opt_out.

Reply via email to