Issue #4 resolved

compile and test tasks may hang if requiring code has non-trivial side-effects

Meikel Brandmeyer
created an issue

Moved from the old repository on behalf of Dave Ray.

See mailing list discussion here: https://groups.google.com/forum/#!topic/clojuresque/HEwcnVd-KDQ

Comments (16)

  1. Meikel Brandmeyer reporter

    I will. In fact I'm working on defining how a task should actually behave on the clojure side. The System/exit will probably move into the Driver together with a shutdown-agents.

  2. Meikel Brandmeyer reporter

    I planned to introduce some test cases that I don't break something and restructure the plugin. But maybe I should do a quick maintenance release of the old style plugin. There are other issues in the pipeline as well.

  3. Dave Ray

    Thanks. Was this compiled with Java 7? When I run the tests, I get:

    Execution failed for task ':astyanax-clj:clojureTest'.
    > clojuresque/ClojureExecAction : Unsupported major.minor version 51.0
    
  4. Dave Ray

    hmmm.. Now I get:

    * What went wrong:
    Execution failed for task ':astyanax-clj:clojureTest'.
    > Could not resolve all dependencies for configuration ':astyanax-clj:clojuresque'.
       > Could not find group:clojuresque, module:runtime, version:1.5.6-SNAPSHOT.
    
  5. Dave Ray

    hmmm... I'm running a test and it doesn't seem to exit. I see the printlns in test_junit.clj. Do you know where those go when gradle runs?

  6. Dave Ray

    Ok. I was just fooling myself. There's still no code in Driver.java or test.clj to call (System/exit) after the tests have completed. At least not on the v1.5.7 branch.

  7. Log in to comment