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 (though at the moment must be Groovy >= 1.5.0)
• Access to the groovydoc tool (this might make stub generation unneeded for you if you're not mixing Groovy and Java)
• Some additional configuration options

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 will unnecessary once stubs include Javadocs, since you can compile your mojo like any other Groovy class)
• The stack trace sanitization feature
• 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).

Will GMavenPlus fix my stub generation issues?

I've not personally ever run into these issues, but for those that have: Probably not. The method of generating stubs uses classes maintained by the Groovy project, which is also they way GMaven works. So if you had problems with it, you'll probably have problems with this as well. If you do encounter issues with stub generation, please drop me a note or raise an issue. I'd be happy to see if it is happening within GMavenPlus (in which case I'll fix it), or if it's not you can create an issue for the Groovy team. Alternatively, you can use the Groovy-Eclipse Compiler Plugin for Maven, which doesn't use stubs.

But which tool is the official one?

Technically, there never was any official (endorsed by Groovy team) plugin for Maven, but GMaven was (and still is) very popular because there were no good alternatives at the time.