Why nobody answers or acknowledges my posts?

[.Santanu Chakrabarti]

Is Clojuresque a dead project? Has the maintainer lost interest in it? I logged one issue with Clojuresque and no one bothered to acknowledge it? Whats the matter here in this group.

I am facing more issue while trying to integrate cider-nrepl middleware with Clojuresque. I am getting apprehensive if I would at all be able to solve them.

Well the current issue is:

Exception in thread "main" clojure.lang.ArityException: Wrong number of args (0) passed to: middleware/wrap-conj-descriptor/fn--443
    at clojure.lang.AFn.throwArity(AFn.java:429)
    at clojure.lang.AFn.invoke(AFn.java:28)
    at clojure.lang.Var.invoke(Var.java:375)
    at clojuresque.tasks.repl$eval905$start_repl_task_driver__907.invoke(repl.clj:16)
    at clojuresque.tasks.repl$eval905$start_repl__910.invoke(repl.clj:9)
    at clojure.lang.AFn.applyToHelper(AFn.java:152)
    at clojure.lang.AFn.applyTo(AFn.java:144)
    at clojure.core$apply.invoke(core.clj:624)
    at clojure.lang.Var.invoke(Var.java:383)
    at clojuresque.Driver.main(Driver.java:49)
:clojureRepl FAILED

FAILURE: Build failed with an exception.

I think start-repl method of clojuresque-nrepl has some serious bug.

[Meikel Brandmeyer]

Hi,

On Fri, Apr 10, 2015 at 10:39:34PM -0700, .Santanu Chakrabarti wrote:
> Is Clojuresque a dead project? Has the maintainer lost interest in it? I
> logged one issue with Clojuresque and no one bothered to acknowledge it?
> Whats the matter here in this group.

Clojuresque is a hobby project competing with other things for time
like my family. I cannot provide 24/7 support. And at the moment I'm on
vacation trying to get back some energy. If that's your definition of a
dead project, I'm sorry. But then clojuresque is dead.

> I am facing more issue while trying to integrate cider-nrepl middleware
> with Clojuresque. I am getting apprehensive if I would at all be able to
> solve them.
>
> Well the current issue is:
>
> Exception in thread "main" clojure.lang.ArityException: Wrong number of
> args (0) passed to: middleware/wrap-conj-descriptor/fn--443
> at clojure.lang.AFn.throwArity(AFn.java:429)
> at clojure.lang.AFn.invoke(AFn.java:28)
> at clojure.lang.Var.invoke(Var.java:375)
> at
> clojuresque.tasks.repl$eval905$start_repl_task_driver__907.invoke(repl.clj:16)
> at clojuresque.tasks.repl$eval905$start_repl__910.invoke(repl.clj:9)
> at clojure.lang.AFn.applyToHelper(AFn.java:152)
> at clojure.lang.AFn.applyTo(AFn.java:144)
> at clojure.core$apply.invoke(core.clj:624)
> at clojure.lang.Var.invoke(Var.java:383)
> at clojuresque.Driver.main(Driver.java:49)
> :clojureRepl FAILED
>
> FAILURE: Build failed with an exception.
>
> I think start-repl method of clojuresque-nrepl has some serious bug.

From your description I cannot see how you configured the repl task in
the build.gradle.

Meikel

[.Santanu Chakrabarti]

Well I am not asking for any resolution just now, but some sort of acknowledgement that it would be answered actually gives some assurance. Also this is a community and I believe lot many people are using Clojuresque so it is not necessary that you should address all the issues. May be someone who faced similar issues before can give some direction.

And below I am copy-pasting my build.gradle file content.

buildscript {
    repositories {
        mavenCentral()
        maven { url 'http://clojars.org/repo' }
    }
    dependencies {
        classpath 'clojuresque:clojuresque:1.7.0'
    }
}

apply plugin: 'clojure'

repositories {
    mavenCentral()
    maven { url 'http://clojars.org/repo' }
}

dependencies {
    compile "org.clojure:clojure:1.6.0"
    compile "cider:cider-nrepl:0.8.0"
    runtime "org.clojure:tools.nrepl:0.2.10"
}

clojureRepl {
    port = "7888"
    handler = "cider.nrepl/cider-nrepl-handler"
}

Also instead of waiting for a resolution to come I have created one work-around taking clue from the discussion below. This work-around is not complaining anything about cider handler.

https://groups.google.com/forum/#!topic/clojuresque/_RSyjFk6bbs

 And I request that there is a bug in Clojuresque 1.7.0 that I reported in a separate discussion here. Please take a look at it when you find some time.

Thanks and regards
Santanu