Yep, gone, sorry. Someone contested the name "Ninja" so I figured it was easier to just rename it. Here is the last JAR and source for Ninja, javadocs included:http://n4te.com/temp/ninja-final.zip
Hope this holds you over until the new projects are ready!
The-project-formerly-known-as-Ninja is being broken into two projects:
Does the serialization. This way the serialization bit can be used without the networking bit, or with a different networking lib. I did some benchmarks and it holds up well against other similar libs (such as Google's protobuf):http://code.google.com/p/kryo/wiki/BenchmarksAndComparisons
I am just finishing up Kryo and starting on refactoring the networking piece.
This is the networking portion. Obviously, it uses Kryo for the serialization. Will be an almost identical API to the-project-formerly-known-as-Ninja.
"Kryo" isn't the best name, but the good names are taken. I was spending way too much time just trying to name it, so Kryo it is! At least it is short...
The HTTP communication portion of the-project-formerly-known-as-Ninja is getting moved to a "client" project the Legion project:http://code.google.com/p/legion/
Legion lets you send/receive objects to/from a servlet just as easily as Ninja/KryoNet. This means it is easy to write turn-based games and desktop or mobile applications that communicate with a webserver. Any webserver will work, but a servlet container lets you use Kryo on the server. Legion supports Google App Engine and will come with some common functionality (user registration, login, sessions, arbitrary data storage).
I'm also working on another project called Skorpios for OpenGL on both desktop and Android with a single codebase:http://code.google.com/p/skorpios/
The code for this was mostly ready a couple weeks ago, but I just recently came up with the name (wanted Scorpion but Skorpios isn't too bad) and have been busy with other things. The code will be up soon!