I just re-read you email and I'm confused by your comment, please clarify if possible. But isn't what I've been hopefully explaining is the creation of a mojo that wraps a command line process. I have written the mojos (agitate and dashboard) an users only need to reference the plugin in their build element. If the defaults are right for them, say they have a 80% code coverage target instead of the default of 70% then they can add a <coverage> element to the <configuration> element for the plugin. Now the plugin takes the prams and puts then in the correct order and that is where I'm currently am. I would like to have a maven-java-plugin or something like it that my plugin can depend on to actually execute the process and tie its output stdout and stderr back to my process. That's all I need. I'm not advocating giving users the ability to execute any java command from their pom.
This is my 1st m2 plugin so if I'm now one of those clueless users, then please correct me where I'm wrong. Wb On 9/20/05, John Casey <[EMAIL PROTECTED]> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > I guess I don't understand what's wrong with writing mojos to wrap > specific command-line-driven use cases...? > > - -john >
