an extended (default) web-app loader (to handle JRuby specific "leaks")
custom-loader - remove BC security provider with a class-loader check
(utilizing JRuby-Rack 1.1.14 API to obtain managed runtimes)
we will now need JRuby's API when compiling trinidad_rb.jas's classes
do some JDBC driver cleanup - for now shutdown MySQL's cleanup thread
"release" JRubyWorkerTimeout (executor) threads by mending class-loader
- their context-class-loader is likely to be set to the web-app's jruby loader
we can depend on jruby-rack 1.1.14 now
do not load any trinidad files when building gemspec
- avoids confusion with Trinidad being defined? when using :git path
we'll do a few internal changes - thus will likely end up with new major 1.5.0
class-loader kung-fu to get thigns right towards leak free applications ...
leave the default loader for .wars
cleanup host lifecycle - remove class-loader spec (no longer relevant)
refactor CommandLineParser as CLI ... and start deprecating some options
remove some of the 'old' deprecated methods from `Trinidad::Server`
reset the jar-path loader gets by default on start
get some Trinidad autoload magic !
allow to disable (inherited) web-app extension by specifying `name: false`
handle `address: *` since it somehow broke on adding a JMX bean with * ...
... in it's name (which is not a valid one)
avoid the extension loading specs bumping into one another
yet another custom slice of travis-ci configuration
a "default" JarScanner based on TC's StandardJarScanner implementation