At 12:14 PM 4/7/2011, you wrote:
... Could you drop a note here of what you sent to me the other day
about the project structure?
sure, here is what i noticed when i tried to use the project:
you have eclipse.classpath and eclipse.project files instead of
.classpath and .project files (which are usual, at least on windoze).
also, groovy lib is /opt/local/share/java/groovy/lib - (maybe use
this is GROOVY_HOME is not defined?)
eclipse is not happy with the project on windoze, so i make a groovy
project and copied the source into a new empty groovy project. no
problems and some of the tests run.
here is what i noticed about the project.
your output path is .settings/bin/ instead of just bin/ (some people
prefer build/ and use bin/ for scripts).
you have java code and groovy code in the same directory. some people
like to put them in different directories (but in the same package).
you have junit 3 tests (groovy test cases) and programs that do
testing but are not testcases (like test shell) in the same
directory, it's nicer to have all of the junit based test classes in
a different directory (but the same package) since you can run all of
the test cases in a package with one right click in eclipse.
looks like you are using:
http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
haven't looked much at the code yet. this is just what i observed in
making a new eclipse project.
thanks
---
co-chair http://ocjug.org/
