The phases are community defined, and there are no plans to ever change that. This is why Maven is easy to understand and use wherever you go - rather than having to learn a bunch of "custom" stuff. If you really want to coallate your work into a single command, try using the "exec" goal: http://mojo.codehaus.org/exec-maven-plugin/
Eric On 12/7/06, Deluigi Marcus <[EMAIL PROTECTED]> wrote:
Hi I want to abuse maven to perform a setup for a testing environment, such as starting derby, starting a tomcat and deploying a WAR file which is another project. Maven does a fine job in downloading all the required software if necessary and building the WAR file which it is another project. Besides, it is platform independent, so I am using it for all these tasks. But I don't want to enter all these commands on the command line all the time. I think a much nicer way would be to add a custom phase (such as 'start-environment') to the module. When I am developing, I would like to be able to execute only this phase, without the life-cycle. Is something like that possible? Of course, I can make a shell-script but I think adding a custom phase to the project would be a nice thing. Greetings Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Eric Redmond http://codehaus.org/~eredmond
