Hi, yes the benchmark is still being maintained. It's updated about once a year right now.
When adding a new library I typically work with the library's author. It's best if you implemented the following interfaces:
RuntimePerformanceFactory, MemoryFactory, BenchmarkMatrix. Then FactoryLibraryDescriptions needs to be updated.
Use the latest SVN code. See implementations inside of jmbench.impl.* for examples of how to do it correctly by looking at other libraries. Then I go over it and discuss any modifications that need to be made. Take a look at
http://code.google.com/p/java-matrix-benchmark/wiki/manual to see how it should be run.
The benchmark is designed to measure the sort of performance the average user can expect. Code which requires intimidate knowledge of the library, especially if the documentation provides a different solution, will raise a red flag. Also use of algorithms which are known to be numerically unstable, but run faster, which no one would use in the general case, are not allowed. There are checks in place which attempt to catch that, but it is possible to sneak by them. The same code should also be used across all matrix sizes, but your library is allowed to do internally whatever it wants.