Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 350449

Summary: [mojo] org.codehaus.gmaven:gmaven-plugin support
Product: z_Archived Reporter: Brad Beck <bradley.beck>
Component: m2eAssignee: Project Inbox <m2e.core-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: andrew.eisenberg, jeff.ramsdale, mail, t-riggs
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:
Attachments:
Description Flags
Sample gmaven-plugin usage project. none

Description Brad Beck CLA 2011-06-27 10:11:14 EDT 
Build Identifier: 20110615-0604

The gmaven-plugin generates java stubs from groovy files. The plugin goals should be executed as part of project workspace build and the generated sources should be added to the build path.

Reproducible: Always
Comment 1 Brad Beck CLA 2011-06-27 10:12:13 EDT 
Created attachment 198651 [details]
Sample gmaven-plugin usage project.
Comment 2 Igor Fedorenko CLA 2011-06-29 02:13:13 EDT 
m2e core development team is looking for help implementing support for various "not covered" maven plugins. If you are interested, wiki [1] provides pointers where to start and we'll be happy to answer questions on m2e-dev mailing list. To avoid duplicate effort, please assign this bugzilla item to yourself if you already work on corresponding m2e extension.

[1] m2e extension development is documented in http://wiki.eclipse.org/M2E_Extension_Development
Comment 3 Andrew Eisenberg CLA 2011-12-22 17:09:14 EST 
The groovy-eclipse configurator is available from discovery and should address your problem.  If you are using groovy-eclipse, the generated stubs should *not* be added to the build path.
Comment 4 Denis Roy CLA 2021-04-19 13:22:02 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/