Changing to jME2.0

I realized i was using 1.0 of jME and have decided to change to 2.0. Are thier any real advantages to using 2.0 over 1.0.



Also I’ve used eclipse to d/l the SVN and use as a project i then created a library named jMEv2.0 required and added all the jars i found in the lib folder jorbis,jinput,lwjgl,lwjgl_util,lwjgl_util_applet, junit, gluegen and jogl.jar. I then set the lwjgl native library for the lib folder. I also made the src folder in the trunk folder set as the source folder, However i realized thier are several src folders and confused in the one I should be using. However after doing all of that i’m still unable to run any apps is their something i’m missing. I set JOGL and LWJGL native library to the native folder in their respective sub folder in lib



btw I’m still kind of new to everything and based everything i did on the wiki tutorial for the 1.0 version.



Also would changing to 2.0 mean i would have to relearn the things i learned in the wiki and remake the scripts I’ve written so far??

Bonechilla said:

i guess I can delete the natives for the other lwjgl jars.


I'm not sure which files your talking about now but i wouldn't delete them... just to be sure  :)
but hey as long as its working who's complaining  :wink:

Hellmaster

I had succussfully downloaded and tested the tutorial examples (jmetest.TutorialGuide.*). Here're my steps (as far as I can remember):


  1. Use Subclipse to check out jME code from SVN
  2. installed Maven
  3. mvn -Declipse.workspace=<path-to-eclipse-workspace> eclipse:add-maven-repo
  4. run libmvn-lib-install
  5. mvn eclipse:eclipse
  6. Refresh eclipse project. Sometimes, you need to clean the project, close it, reopen, and refresh, in order to get rid of the complains that eclipse cannot find the jars.



    Good luck!
changzhouwang said:

I had succussfully downloaded and tested the tutorial examples (jmetest.TutorialGuide.*). Here're my steps (as far as I can remember):

1. Use Subclipse to check out jME code from SVN
2. installed Maven
3. mvn -Declipse.workspace=<path-to-eclipse-workspace> eclipse:add-maven-repo
4. run libmvn-lib-install
5. mvn eclipse:eclipse
6. Refresh eclipse project. Sometimes, you need to clean the project, close it, reopen, and refresh, in order to get rid of the complains that eclipse cannot find the jars.

Good luck!

May I ask what is Maven i heard of it before checked the site but it still feels pretty ambiguous to me btw can i ask why their are so many src folders which one is the proper one to use?

There should be only one source folder, if u have multiple i think you forgot to check the box to allow output folders for source folders or something like that. Installation of JME2 is almost the same as JME1 http://www.jmonkeyengine.com/wiki/doku.php?id=setting_up_eclipse_to_build_jme only things changed is the repository and some minor changes in the libraries.



The jars that require natives are gluegen, jogl and lwjgl.



Hellmaster.

thx I deleted the whole project and re downloaded it using http://jmonkeyengine.googlecode.com/svn/trunk/ before i used http://jmonkeyengine.googlecode.com/svn/. I figured out the natives thing but i did it for all the lwjgl and glugen,jogl prior and it started to work but i guess I can delete the natives for the other lwjgl jars. thx btw

Maven is a project management tool, apparent used by jME 2.0. In a nutshell, it manages jar file dependences in a much clean way than Eclipse or Ant. You can take a look at http://maven.apache.org/guides/mini/guide-ide-eclipse.html and maybe some general guide in the related links.



I am not an expert of Maven. Currently, I only use it to create Eclipse project (using mvn eclipse:eclipse) for simple projects with pom.xml (the project object model used by Maven).



If you have many related projects with inter-dependency, Maven will be a really good tool as it simplifies your job of maintaining the dependencies, especially when these projects evolves with different versions.

Use Subclipse to check out jME code from SVN
2. installed Maven
3. mvn -Declipse.workspace=<path-to-eclipse-workspace> eclipse:add-maven-repo
4. run libmvn-lib-install
5. mvn eclipse:eclipse
6. Refresh eclipse project. Sometimes, you need to clean the project, close it, reopen, and refresh, in order to get rid of the complains that eclipse cannot find the jars.


It took me quite some time to find these instructions - wouldn't it be nice to mention this in the wiki? I followed the "setting up eclipse" guide and did not even realize I was using jME 1.0 not 2, and then when I found out I tried to somehow get those libs in my repo until I found this...