Added a FitNesse tests for the MBean that gathers statistics about the Extractor
Extracted the Extractor class
Added Guice to the jmx-extractor project
Modified the extractor web app to create and configure an Extractor.  The Extractor is configured using a settings file pointed to by JNDI.  The Tomcat in the fitnesse project specifies the file in JNDI.  Not everything is working just yet.
Run FitNesse tests in a Maven profile of their own so that tests aren't run with the FitNesse wiki is launched.  This way you can launch the wiki when there are failing tests (such as during fixture development).
The jmx-extractor-webapp can now read the configuration that is configure in Tomcat's JNDI Context
Demonstrated that when the Extractor is run in its own web application, it can extract MBeans from another web application.  This required that the Extractor run periodically.  I also introduced logback and SLF4J for logging.
Merge pull request #8 from DavidWhitlock/master

Demonstrate that the Extractor can harvest stats from another web application