I catch this message. > <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. >
This message talked about the groovy plugin that was published on the cocoon mailing list. The one that is on the sandbox is a native maven plugin, not a proxy. groovy(s) are directly compiled. There are special plexus extensions (plexus sandbox). One to generate the plugin descriptor from the sources and an other one to define a new plexus-compiler. The resulting plugin is packaged like a java plugin (.class + descriptors). regards.
