Hi Jason,

Sorry it got dropped. Lots of stuff to process, and I don't know how
many Groovy users we have here. It's definitely an interesting thing to
have.

A while back, Éric Burghard (who it was noted on the issue was working
on something similar) contributed some code to the mojo-sandbox. How
does your compare on features to that?

I'd be more than happy to have you added to mojo & plexus to bring this
all together and work on jython if you are still willing.

Might be better to post to [EMAIL PROTECTED]

- Brett

Jason Dillon wrote:
> Hi guys, a few months back I implemented support to allow Mojos to be
> written in Groovy.  I've submitted the code to Maven and its just been
> sitting in the MNG Jira going no where.  I was thinking that perhaps
> these components could live in mojo.codehaus.org, and published to the
> codehaus repo, so that people can actually start using it.
> 
> FYI, the issue is here:
> 
>     http://jira.codehaus.org/browse/MNG-1664
> 
> Its basically just a set of modules, w/support to write Mojo's
> w/Groovy... and *extend* from other .groovy or Java classes from the
> .jar... and the main .groovy can be annotated with javadoc tags to
> generate the plugin descriptor too.
> 
> I've also got most of the work done on Jython support, but kinda lost
> interest because its talking so long for the finished Groovy stuff to
> get added.
> 
> Any thoughts?
> 
> --jason
> This email and any attachment(s) thereto, are intended for the use of
> the addressee(s) named herein and may contain legally privileged and or
> confidential information under applicable law. If you are not the
> intended recipient of this e-mail, you are hereby notified any
> dissemination, distribution or copying of this email, and any attachment(s)
> thereto, is strictly prohibited. If you have received this communication
> in error, please notify the sender at 415-281-2200 or via return e-mail at
> [EMAIL PROTECTED] and permanently delete the original copy
> andany copy of any e-mail, and any printout thereof. Thank you for
> yourcooperation.
> 

Reply via email to