I’ve also looked into it deeper and have found a workaround for travis, but that’s linux-only then firstly.
I wonder what happens if you take the gradle template and just specify jme3-jbullet as dependency, you should also experience that problem?
So what’s the case: These POM Entries are new
We have jbullet as jar in our libs directory, however it’s not known to maven as
jbullet:jbullet, it’s just there.
This means, I’d do an
mvn install:install-file -Dfile=jbullet.jar -DgroupId=jbullet -DartifactId=jbullet -Dversion=0.0.1 -Dpackaging=jar
@Momoko_Fan Any Idea what a better solution would be?
The SDK itself isn’t really broken but I’ve decided against dropping jbullet because of that, so that SDK users can debug their physics problems by simply swapping out jbullet and bullet-native.
So removing jbullet is not a good workaround
Edit: Further Investigation has shown that the actual problem seems to be that jbullet did not mention a version and hence it couldn’t even be parsed.