I’ve used enclojure for a long time (in internet years). It has always seemed a bit finicky. However, with the 1.4 release and the switch to using Maven as the build tool, things stopped working. Projects that had worked fine before no longer compiled or executed. The “Getting Started” section of the enclojure web page appears to be hopelessly out of date and actually misleading. Here’s what I had to do.
System: NetBeans 6.9.1, enclojure 1.4, Apache Maven 2.2.1, Java jdk 1.6.0_23, Encoding Cp1252, Windows XP, 32-bit or Windows 7, 64-bit
- Create a new clojure 1.2 project.
Paste the source of a canonical Clojure program. I like this program because it uses Clojure, has interaction with Java, uses a macro, and generates a runnable jar using AOT compilation – or should.1234567891011121314151617181920212223242526272829303132(ns net.dneclark.JFrameDemo(:import (javax.swing JLabel JButton JPanel JFrame))(:gen-class));;; This is a small app to demonstrate how to create;;; a swing-based user interface from Clojure. It is;;; stolen almost completely from Stuart Sierra's;;; post at stuartsierra.com/2010/01/03/doto-swing-with-clojure(defmacro on-action [component event &amp; body]`(. ~component addActionListener(proxy [java.awt.event.ActionListener] (actionPerformed [~event] ~@body))))(defn counter-app (let [counter (atom 0)label (JLabel. &quot;Counter: 0&quot;)button (doto (JButton. &quot;Add 1&quot;)(on-action evnt ;; evnt is not used(.setText label(str &quot;Counter: &quot; (swap! counter inc)))))panel (doto (JPanel.)(.add label)(.add button))](doto (JFrame. &quot;Counter App&quot;)(.setContentPane panel)(.setDefaultCloseOperation JFrame/EXIT_ON_CLOSE)(.setSize 300 100)(.setVisible true))))(defn -main (counter-app))
In the project view, right-click on the project name, then select “Properties” from the drop-down menu.
- In the “Run” branch, in the “Main Class:” edit box, type “net.dneclark.JFrameDemo”.
- Edited project pom.xml to include 2.0.2 under the maven compiler plugin as suggested by this thread from the enclojure discussion group.
For one of my systems, this is all it took. On another system, there was something funky in the Maven repository. Deleting the repository and re-building got things working.
At this point, the executable jar is called “sample-0.0.1.jar”, to rename it, open the project properties, change the Artifact Id to “JFrameDemo”. Executable jar is named “JFrameDemo-0.0.1.jar”.
This jar is not a stand-alone executable as it typically created by NetBeans. It does not contain any of the libraries, such as the Clojure libraries.