[ http://jira.codehaus.org/browse/MNG-472?page=comments#action_41339 ]
Brett Porter commented on MNG-472: ---------------------------------- IMO, executions only apply to mojos with a phase binding. It's all about the lifecycle. This has nothing to do with the command line. basically, the command line is a one goal lifecycle, so the executions have nowhere to bind, and so they are separate. The general plugin configuration is picked up, however - just not any of the exec. config. Maybe, looking back, the executions name is misleading, because two executions don't actually mean that. It is two different configurations of a goal, bound to the one lifecycle. Hopefully I can polish off the lifecycle doc early tomorrow, and that will clear it up. > multiple <execution/>'s with no goals not considered when running a goal > directly from the CLI > ---------------------------------------------------------------------------------------------- > > Key: MNG-472 > URL: http://jira.codehaus.org/browse/MNG-472 > Project: Maven 2 > Type: Bug > Components: maven-core > Reporter: John Casey > Assignee: John Casey > Priority: Critical > Fix For: 2.0-beta-1 > > > assume you specify a plugin in the pom with multiple <execution/> sections, > each containing configurations. > It should be possible to directly invoke a goal within this plugin, and have > that goal run once per execution, despite the fact that the goal is not > explicitly specified in the <execution/>. > This is not the case now. > Workaround: specify the goal for each execution in which you want it to run. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
