There is one big difference between a plugin and an ant-script that is run via ant-tasks (I think you meant a ant-run plugin here?):
Maven plugin is *based* on the standard build lifecycle and is by definition reusable (standard declaration and is kept in a repository, again at the standard location) while ant is an ad-hoc solution (you have to copy/paste the script to reuse it). On Sun, Mar 23, 2008 at 4:22 PM, Graham Leggett <[EMAIL PROTECTED]> wrote: > Saloucious wrote: > > > i would like to know what is recommanded by Maven Team when a procces > does > > not fit with any plugins/goals provides by Maven. > > > > Just for example, if i want to touch a file, what is better : create a > > my.company.plugin.touch or add a simple antrun task ? > > I don't think it matters much - on condition the ant script doesn't > violate the maven design rules. > > I have noticed though that people who write ant scripts like adding > arbitrary and undocumented requirements onto other developers, > especially when it comes to some weird directory structure that you > need, or hard coded paths in the development environment. > > Writing a maven plugin instead can prevent many of these headaches in > the long term, although it might mean more work in the short term. > > Regards, > Graham > -- >
