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?
Wb On 9/20/05, John Casey <[EMAIL PROTECTED]> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 [Snipped] | > | 3. Need to do a myriad of simple things such as automatically run java > | command or deploy to tomcat. I used to do this all the time in my ant > | scripts, ie run my build.xml script and at the end it would run my app > | on completion. It's a credit to those on this list who reply with ideas > | and workarounds - however this is kind of related to 2 above, where > | there are lots of ant tasks out there that are tested to death and that > | I should be able to use today. > > The funny thing about Maven 2 is that it facilitates external plugin > development. You can load a plugin from a repository hosted anywhere. > Personally, I feel strongly that executing random commands from within > the build process is a Bad Thing, and a thing that is bad and common > with Ant. Maven - and also Ant, to a lesser extent - is a build tool. > It's not a launching platform, and it's not a tool to be used to run > your coffee maker. Executing random commands from a configuration in a > POM is: > > a. unscaleable, since that runtime config is not encapsulated for reuse > > b. bound to partition your build logic into multiple pieces, which now > have to be maintained from multiple sources. > > In Ant, you can do anything you please, including things that don't > relate to the process of building software. It's important to keep a > clear idea of the problem domain we're trying to address here. > > Having said that, there's nothing stopping you from hosting your own > maven-foo-plugin on Sourceforge or somesuch. If you find what you > perceive to be a hole in our plugin offering, and cannot convince us to > fill it, there's nothing stopping you from scratching your own itch. We > currently have maven-execute-plugin on the mojos project, but I'd really > like to see it deprecated and eliminated eventually. > >
