hi Geoffrey, quite clear now!thank you so much!
my last doubt, the only way to specific a plugin to execute in certain phase, is to add a execution section? got any other way? oliver.lee 2008-06-20 发件人： Geoffrey Wiseman 发送时间： 2008-06-20 09:38:19 收件人： Maven Users List 抄送： 主题： Re: what is difference between configuarion and execution of plugin ? On Thu, Jun 19, 2008 at 9:30 PM, oliver.maven <[EMAIL PROTECTED] > wrote: > hi, > i know execution may contains configuration,but i am still confusing, > > some plugin has the configuration only,some plugin has the execution only, > and some has both of them, > > how to differentiate them and use correctly? > > thanks a lot! Configurations provide additional, project-specific information to the plugin so that it can do what you want it to do whenever it is run. Executions allow you to to cause the plugin to be run at particular points in the build lifecycle. Configurations can be general, affecting the plugin at all times, and/or execution-specific. So, for instance, I use the Cargo plugin in my project. I supply it with enough configuration that it knows to load my project using Tomcat 5.5 and make it available on a particular URI. That allows me to type "mvn cargo:start" from the command-line and have the project up and running, and cargo waits for my signal to exit. However, I also have executions for cargo so that before the integration test phase begins, cargo starts up, and stays running. After the integration tests, cargo shuts down. These have a few additional configuration settings, but the important part of this is the binding to the integration-test phase of the build lifecycle. Does that make more sense? -- Geoffrey Wiseman
