New release is up! Version 1.4.0

[Eric Thorsen]

Some key items for this release:

Fixed the navigator.

Fixed the new maven projects and created 2 versions.  One for Clojure 1.1 and one for Clojure 1.2

Added in the patch to make the color coding editable with the Netbeans convention (thanks to jmis).

If you already have the updatesite setup, you should see this in your list of available updates. Otherwise, go to:

www.enclojure.org

for details on how to get setup.

Sorry I've been a bit quiet recently...busy season for me :)

Thanks again for all the feedback and the recent contributions!

Eric

[Mark Engelberg]

It's great to see the new version.

I'd like some help understanding what I'm looking at in the default
project. I started the wizard with a default namespace of
com.mycompany.main

This creates a main.clj under Source Packages/com.mycompany
A main.clj under Test Packages/com.mycompany
main.clj under Other Sources/src/main/clojure (clicking on this seems
to lead to the same file as the one under Source Packages).
main.clj under Other Test Sources/src/test/clojure (clicking on this
seems to lead to the same as the one under Test Packages).

1. What's with the Other Sources, Other Test Sources files? What
purpose does it serve, and why does it seem to link to the same files
as in the other packages?
2. When I add a sample test to the Test Packages main.clj file,
running the tests (Alt-F6) still reports that no tests were run. I
notice that the main.clj in Test Packages doesn't match the name of
the namespace (com.mycompany.main-test), so I'm wondering if this
could be why it's not finding the test?

What is the purpose of the pom.xml file? Do you edit this directly or
is it always managed for you entirely?

Thanks,

Mark

[Eric Thorsen]

On Sep 10, 11:44 pm, Mark Engelberg <mark.engelb...@gmail.com> wrote:
> It's great to see the new version.
>
> I'd like some help understanding what I'm looking at in the default
> project.  I started the wizard with a default namespace of
> com.mycompany.main
>
> This creates a main.clj under Source Packages/com.mycompany
> A main.clj under Test Packages/com.mycompany
> main.clj under Other Sources/src/main/clojure (clicking on this seems
> to lead to the same file as the one under Source Packages).
> main.clj under Other Test Sources/src/test/clojure (clicking on this
> seems to lead to the same as the one under Test Packages).
>
> 1.  What's with the Other Sources, Other Test Sources files?  What
> purpose does it serve, and why does it seem to link to the same files
> as in the other packages?

This is something related to the Maven project view in NB. I'm afraid
I do not know much more about it than that. Anything under the src
dir appears there.
You can ignore the other sources if all your stuff stays under the src/
main/clojure dir (which it will if you add files via the IDE)

> 2.  When I add a sample test to the Test Packages main.clj file,
> running the tests (Alt-F6) still reports that no tests were run.  I
> notice that the main.clj in Test Packages doesn't match the name of
> the namespace (com.mycompany.main-test), so I'm wondering if this
> could be why it's not finding the test?

That is wired to the Java test (I believe).
If you right click on the project, go to Custom and select goals, you
can setup the clojure.test goal for your project. Make sure you check
"Remember as" and put in clojure:test.
Then you wil be able to run the goal from the custom menu.

>
> What is the purpose of the pom.xml file?  Do you edit this directly or
> is it always managed for you entirely?

You can use the Add Dependency helper stuff within Netbeans to search
for libraries for you project and never have to touch the pom.xml.
The answer to the rest of your questions regarding pom.xml files are
about learning a bit about maven. I used the Sonatype site to do
this.
http://www.sonatype.com/books.html

>
> Thanks,
>
> Mark

[Mark Engelberg]

On Fri, Sep 10, 2010 at 8:59 PM, Eric Thorsen <etho...@enclojure.org> wrote:
> That is wired to the Java test (I believe).
> If you right click on the project, go to Custom and select goals, you
> can setup the clojure.test goal for your project. Make sure you check
> "Remember as" and put in clojure:test.
> Then you wil be able to run the goal from the custom menu.

This caused errors, but I figured you might have meant to put
"clojure:test" as opposed to "clojure.test" as the goal also, so I
tried that. With that in place, running the goal from the custom menu
seemed to work, and it said it was testing com.mycompany.main, but
then it reported that it ran 0 tests containing 0 assertions, even
though I have added:
(deftest addition
(is (= (+ 2 3) 5)))
inside the com.mycompany.main-test namespace.

Any ideas?

Thanks,

Mark

[Eric Thorsen]

Sorry about the typo...
I'm not that familiar with how the Clojure maven plugin works. I tried
adding the testSouceDirectory in the config section for the plugin but
that did not help.
The answer is probably in the clojure.contrib project for which there
are tons of examples of running tests with the maven clojure plugin.

Eric


On Sep 11, 12:09 am, Mark Engelberg <mark.engelb...@gmail.com> wrote:

[Mark Derricutt]

Just found this post - just about to run off for lunch but when I come back I'll read over this thread and see if I can figure out whats going on.

If I need to patch/update the maven plugin I will...