> -----Original Message----- > From: Wendell Beckwith [mailto:[EMAIL PROTECTED] > Sent: mardi 20 septembre 2005 19:15 > To: Maven Users List > Subject: Re: [m2] reasons for sticking with maven > > John is basically stating the very thing that I'm against in the statement > below. I have a 3rd party command line utility from > www.agitar.com<http://www.agitar.com>, > that basically does unit tests against our code. I want to write (and have > started writing) an M2 plugin to execute the java command line for the > agitation process from my plugin. All I need now to complete my plugin > besides more hours in a day is a plugin that will allow me to execute a > java > command line. Now my plugin will integrate with the maven lifecycle during > the test phase. However, first I'm told to use the maven-execute-plugin > and > then another dev states that it's bad and wants to see it eliminated, I'm > left thinking WTF!? This *helps* me adopt maven and the process, not > hinders > it. My whole purpose for writing the plugin was so that I could make the > plugin once and the other groups here and else where since I would open > source it would be able to reuse it. Is this not what maven is for?
Just to muddy the waters: why don't you use commons-exec from your plugin's java code to execute your process? [snip] Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
