i noticed you changed the junit lib path to "jME Physics 2/impl/ode/lib", while the one for the jre is "jmephysics/impl/ode/lib"
this breaks the junit native lib config here. i wonder if this can't be done with some eclipse workspace variables otherwise this doesn't make sense unless everyone calls his project "jmephysics" (like in the cvs) or "jME Physics 2" (the way you have it locally)
err, well I just applied your patch - I'm not an eclipse user - that xml made sense to me… but now you're talking about it I notice that difference in naming… what should be done? Change "jmephysics" in your patch to "jME Physics 2"?
i would recommend jmephysics as it's the same name as the cvs module. otherwise users would have to check out in a folder named "jME Physics 2". if they don't, the build path would be broken. if they repair it, they change the CVS monitored file.
so change/leave it to jmephysics, and if there are complaints, either remove the file or point them into the right direction. but i assume there won't be many complaints.
By the way, I remember something similar happening with the dependence from jME that there is in jmephysics. I checked out as 'jme' (lowercase) and the dependence in jmephysics is to 'jME' (M and E uppercase).
Anyway, this is not really a problem, but that's why I don't upload the IDE project descriptors to repositories.
@jjmontes: true, thought it was easier for newbies to set it up this way - when you think it makes it more complicated I would remove them entirely… (which would break their configurations once again, btw)
The problem is you don't have to set the library path as VM arguments all the time
if you set the native library location when you add the library.
I have done this little howto use jME-physics with eclipse
and this makes your change in the .classpath unnecessary.
the library is already added by default.
where's the howto?
but a problem occurs if you give you local copies another path then workspace/jME and jME physics 2
if you are new to eclipse and gave them other names it can create some frustration with this .classpath.
none of my projects are in the eclipse workspace path.
as of the naming, i think it is more probably that people will name their projects like the cvs module than some other naming combinations. if they don't use those names, they will have to set up the paths. that's the worst case. otherwise they'll just have a running configuration which is better than nothing ;)