2011/3/31 Armando Blancas
> > So, really, all the current ccw behaviour wrt auto-compile, in background
> or
> > not, concept of "Clojure Application" will be reworked.
>
> One thing that ccw handles with ease is compiling Java for use right
> there in Clojure. With auto-compile one could do the
> So, really, all the current ccw behaviour wrt auto-compile, in background or
> not, concept of "Clojure Application" will be reworked.
One thing that ccw handles with ease is compiling Java for use right
there in Clojure. With auto-compile one could do the opposite just as
easy for dependent pro
2011/3/31 Armando Blancas
> > Your problem is probably that you only export the clj file. But the clj
> file
> > corresponds to a namespace with a gen-class. A gen-class must be
> compiled.
> > And yours is probably not.
>
> I'd think that's what the ccw.builder is there for.
More or less. What
> Your problem is probably that you only export the clj file. But the clj file
> corresponds to a namespace with a gen-class. A gen-class must be compiled.
> And yours is probably not.
I'd think that's what the ccw.builder is there for. Then it'd be up to
the user to decide what to export. Having
Hi,
Your problem is probably that you only export the clj file. But the clj file
corresponds to a namespace with a gen-class. A gen-class must be compiled.
And yours is probably not.
The more I use clojure with java interop, the less I'm tempted to play with
gen-class when I'm not forced to.
Why
This has worked for me. Modify depending on your case.
CAVEAT: I built a fatjar using $ lein uberjar which I then added as an
external dependency in Eclipse. This included the clojure jar, the
contrib and potentially lots of other stuff I had in my project. It is
not entirely clear to me if one ne
