On Tue, 2005-09-20 at 13:09 -0500, Wendell Beckwith wrote: > 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.
For now, until all the hot air in commons-exec stabilizes take a look at plexus-utils and the org.codehaus.plexus.util.cli package. For a simple example take a look at [1]. [1]: http://svn.apache.org/viewcvs.cgi/maven/continuum/trunk/continuum-core/src/main/java/org/apache/maven/continuum/utils/shell/DefaultShellCommandHelper.java?rev=227315&view=markup -- Trygve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
