GMaven Migration

##FAQ For Users Migrating From GMaven## A special welcome to you! I hope you find that this plugin meets your needs. Here's the answers to some questions you might have about your migration.

What does GMavenPlus provide that GMaven doesn't?

• Uses whatever version of Groovy your project does
• Access to the groovydoc tool (this might make stub generation unneeded for you)
• Additional configuration options to classes in org.codehaus.groovy.tools

What's not in GMavenPlus that was in GMaven?

Below are the items I don't plan on implementating at this time. However, if these features are important to anyone (or my assumptions are flawed), I'll gladly reconsider.

• The ConsoleMojo
• The ShellMojo
• The GroovyMojo (this should be unnecessary since you can compile your mojo like any other Groovy class)
• The stack trace sanitization feature (I couldn't see that this actually did anything)
• gmaven-archetypes and gmaven-examples (I thought the usage is so simple that between the Maven site and the integration tests these aren't really needed).