m2e Eclipse plugin settings - lifecycle execution not covered error in Eclipse sorted out by this
 #85 reimplementing NativeLibraryLoader
- simplified, only loading from embeded resource
- fixes issues with redeployment in J2EE environments, since this method
  now effectively creates new so temp file each time it is invoked. All
  of the temp files then get deleted on web container shutdown
- dropped library name from the method too, only using the filename of
  the so library to load
- updated all client code
- deleted unnecessary suppres warnings (Eclipse warned about, no reason
  really for them)
Merge pull request #101 from PoJD/features/nativeLoader

MERGED:  Reimplementing loading native library

I'm a little concerned that removing the native system loader logic where it would first attempt to load the library from the existing classpath or manually configured library path may negatively impact some users?  While this was not the default path for loading the native .SO file, it did provide an alternative method to manually copy the .SO file to a system libs path or allow users to include the command line argument "-Djava.library.path=" to manually specify a path.  Maybe my concerns are theoretical so I'm willing to merge this change and see if it impacts anyone in a negative way.  If it does we may need to re-include some ability to load the native lib from a configured path (perhaps in a friendlier way that does not rely on exceptions).

Thanks for this work!