Happy birthday! Eric Redmond wrote: > Oh, right! I feel silly for asking now... thanks. > > Of course I'll contribute when I feel more comfortable with its stability. > > I'll get back on this tomorrow... its my birthday today :) > > Thanks! > Eric > > On 11/26/05, Brett Porter <[EMAIL PROTECTED]> wrote: >> The project building the plugin can add this without modifying the >> original plugin plugin: >> >> <plugins> >> <plugin> >> <artifactId>maven-plugin-plugin</artifactId> >> <dependencies> >> <dependency> >> <groupId>...</groupId> >> <artifactId>maven-plugin-tools-ruby</artifactId> >> <version>...</version> >> </dependency> >> >> >> We'd be very interested in this support. Are you willing to contribute >> it back to the project? >> >> Cheers, >> Brett >> >> >> Eric Redmond wrote: >>> Maven developers: >>> >>> I have just completed a couple projects to add Ruby support for Maven 2, >>> allowing one to write mojos in Ruby as well as generate mojo descriptors >>> based upon RDoc markup. But I have run into a hurdle. I currently am >> making >>> the plugin:descriptor run my RubyExtractor by adding the >>> maven-plugin-tools-ruby project to the maven-plugin-plugin dependency >> list. >>> I figured when running the descriptor goal on the plugin project, it >>> populates the mojoDescriptorExtractors with those injected by Plexus, >> which >>> naturally must exist in the classpath space (I believe I am correct >> here). >>> So my question is: is there another way I am missing in which to add my >>> RubyExtractor to the plugin "descriptor" which does not include >> modifying >>> the maven-plugin-plugin project in any way? >>> >>> Thanks! >>> Eric >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
