You're welcome. I hope that I broke nothing during the process. I had to provide different implementations for a few things (view port dimension retrieval, ...).
It depends on your own code base. Expect some minor changes in the import clauses in input manager, for example if you use com.ardor3d.input.logical.TriggerConditions. I'll have to find some alternatives to dictionaries and immutable data types.
P.S: I've reopened the bug report about Guava. I'd like to remove this library from more sub-projects as a first step. The more I think about that, the more I find some solutions :) I'll probably ditch immutable lists, sets and maps :)
Please note that I plan to remove the project from Github on the long term. At first, as I'm an honest man, this project is declared as a fork of the legacy Ardor3D, that's why several features are disabled (search in the code and commits, ...) and you can't find directly the project when searching it by using the internal search engine. Secondly, the term "Ardor3D" started to be used for a completely different purpose on the precious website whose domain name is "ardor3d.com". Thirdly, I don't want to give my pseudonym for the ESTA, I have to get rid of my Github account. You'll have to use the JogAmp GIT repository to get the updated source code here: