|
|
|
That's interesting. Do you have more documentation or examples somewhere? I think we're trying to do two separate things with our plugins. Yours appears to allow you to use (J)Ruby as a language in which to write mojos. Mine is more of a launcher/helper that uses some of the features I just built into trunk. For example, the RakeMojo allows you to attach and run a Rakefile to any phase of a project's build.
I can rename mine away from the current name to avoid confusion. Is there room in the world for both plugins? There is always room for more functionality. Why not just add your mojos to the existing jruby-maven-plugin? I suggest this, because ultimately, the JRuby plugin will likely be added into the core Maven plugin set, like Beanshell or Ant support.
That's a good idea, maybe I'll do that. I'm relying on unreleased functionality in the mojos right now, so maybe I'll keep it in JRuby svn for now, and move it over after 0.9.3.
|
||||||||||||||||||||||||||||||||||||||||||||
http://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/jruby-maven-plugin/