Eclipse Guide to JME (setting_up_eclipse_to_build_jme)
http://www.jmonkeyengine.com/wiki/doku.php?id=setting_up_eclipse_to_build_jme
section “Compiling into JARs” explains to:
build.xml → Run As → 2 Ant build… → check dist-all → check dist-test → Apply → Run
build.xml does not seem to contain “dist-all” nor “dist-test” targets
when I try running “all” I seem to be getting X11 errors from shared applications
we have no wonderland imports… or X11 stuf… so not sure where that's coming from. Also, our ant file does have dist-all. (line 94 or so)
just for kicks you might try typing "java -version" on the command prompt and see what that returns.
yes you are quite correct;
for some reason it would seem that my Eclipse workspace is somehow not correct
when I display build.xml Eclipse editor window does show your correct JME build.xml
however right click on the same build.xml "Run As" seems to run the wonderland build for some reason
thank you for responding!
from standard MS-DOS:
Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.
C:Documents and Settingsmichael>java -version
java version "1.6.0_03"
Java™ SE Runtime Environment (build 1.6.0_03-b05)
Java HotSpot™ Client VM (build 1.6.0_03-b05, mixed mode, sharing)
within Eclipse I did change to specify the JDK instaed of the default JRE
I realize that this would most likely be quite out of the realm of JME,
however this is quite wierd (seems to be Eclipse specific)
JME project build.xml (right click) > "Properties" shows path: /jme/build.xml
JME project build.xml (right click) > "Run As .…" results in "Edit Configuration and launch" dialog
which shows Name: lg3d-wonderland build.xml
same build.xml file, different right click results
I've run into difficulty before within Eclipse workspaces
I was working in Eclipse doing Wonderland
previous to checking out JME from CVS
it would seem that for some reason Eclipse only halfway specified build.xml for the CVS download
on previous occasions when I ran into problems with a corrupted Eclipse workspace
I restarted with a new clean Eclipse workspace
my experiences have been that its a good thing that Eclipse
allows such workspace pointer specification upon starting their IDE
Instead if you use the "Ant" view and drag your build.xml into it you can better rely on the results.
Window -> Show View -> Ant
found it: