Split grinder-groovy into its own module

I split the code necessary to support groovy for test scripts into its own
module. I also reformatted the code to make it match the checkstyle for The
Grinder.

The repository is hosted here:
https://github.com/DealerDotCom/grinder-groovy

I've worked on documentation for it as well, and we are using it internally
and putting it through pases on a few of our internal projects. The scripts
that we write here and will have a bunch of example scripts ready for it as
well.

For this project, I used the net.sf.grinder namespace for the packages
because the eventual goal is to get it accepted as its own module of The
Grinder - but the groupId of the artifact is using com.dealer instead of
net.sf because we may end up doing a release of this plugin prior to it
getting to an acceptable point to be considered part of The Grinder and
obviously we can't release under the groupId that we don't control :)

We're using it internally and after tweaking a couple of minor issues it's
working fine against the grinder 3.8 and 3.9.1 (and 3.10-SNAPSHOT).

At this point it seems that what is remaining to get it considered for
including into the main grinder project is documentation, an xsl for the
tcp proxy, and some time to have it bake and work out any issues - anything
else we should be working on to get it ready for eventually handing over?

Ryan

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

_______________________________________________
Grinder-development mailing list
Grinder-development-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/grinder-development