On 1/12/06, Brett Porter <[EMAIL PROTECTED]> wrote:
Jason Dillon wrote:
> I put my initial analysis of his work in the issue just after it was
> brought to my attention.
I think he went more towards the solution you had with some direction.
He may have even used your stuff for all I know :)
> I can take another peek to see if anything has changed.
Ok, let us know how it goes. I will try and pay some more attention, and
I know there are a couple more people here now that are interested in
such things - Eric B (Groovy), Eric R (Ruby), Jeff (Groovyc mojo). James
Strachan is here for retroweaver and surely has an opinion too :)
As for the Ruby plugin, there is a project rubytools-maven-plugin, which contains the plugin for generating the plugin.xml from the *.rb script source annotations. There is also a rubyarchetype plugin, which I will gladly retire when the normal archetype supports the features I need (which implementing is pretty low on my priority list right now).
I originally designed the rubyscript-maven-plugin to work like the other plexus-*-factory components, which after much difficulty, I decided to just hack it to make it work. Eventually I'll make a full ruby plexus component, but for the time being it is very maven-centric.
As far as a ruby plugin importing code from another plugin, that has yet to be implemented. Its a little more difficult since ruby doesn't really have jvm access, made even more difficult since -- although you could theoretically mix-and-match mojo inheritance hierarchies through Java-based languages (groovy mojo->java mojo->bsh mojo) -- non-_javascript_ing languages must stand alone. But the least I can do is allow ruby plugins to extend/use other ruby plugins.
