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

No worries... it happens ;-)

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 put my initial analysis of his work in the issue just after it was brought to my attention.  

<snip>

So, Éric Burghard basically wrote a proxy from Java to a .groovy, where as the modules attached to this issue provide plexus-level support for binding Groovy objects a first-class components... and provide tools to scrape plugin.xml details directly from the .groovy source.

I however don't have an archetype... haven't figured out how to make one of those yet 

</snip>

I can take another peek to see if anything has changed.

One of the key differences that I made sure to implement was that the Groovy Mojo could extend/use other Groovy sources from the plugin... which required some changes to Groovy to support that I helped get pushed through by working with the Groovy team.

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.

Sure, I'm still willing.

--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 and any copy of any e-mail, and any printout thereof. Thank you for your cooperation.


Reply via email to