2011/3/31 Armando Blancas <[email protected]> > > 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 it /should be doing/ is one thing, what it is /currently doing/ is another thing ;-). > Then it'd be up to > the user to decide what to export. Having to launch the file in a REPL > and type (compile 'com.tiny) seems out of place in Eclipse. > Currently, another option is indeed to launch a Clojure application not from the file's, but from the project's node in the package explorer (I mean, launch from the contextual menu of the project's root, not the contextual menu of the file). The contextual menu of the project's root will activate both auto-compilation-on-file-saved and auto-compilation-on-clojure-application-startup behaviours). Having ccw auto-compile in the background all the project namespaces (or a reduced set of namespaces if it has the information) is on the short TODO list after having released 0.2.0 final. And there will also be the problem of wether ccw can continue to auto-compile in the background when the user has started a Clojure Application which may lead to conflicts on the generated classes of the project's classes/ folder. So, really, all the current ccw behaviour wrt auto-compile, in background or not, concept of "Clojure Application" will be reworked. Cheers, -- Laurent -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/clojure?hl=en
