[
https://jira.codehaus.org/browse/MNG-5090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=347451#comment-347451
]
James Garrison commented on MNG-5090:
-------------------------------------
How do I vote to reopen this issue? I should not have to write my own plugin
to sequence several steps in the build process that are required for Continuous
Integration (test database setup and population).
> Maven End Users should be able to control the execution order of plugins
> without creating a custom Lifecycle and Package Type
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: MNG-5090
> URL: https://jira.codehaus.org/browse/MNG-5090
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Plugins and Lifecycle
> Affects Versions: 3.0.3
> Reporter: Graham Lea
> Assignee: Benjamin Bentmann
>
> As [confirmed by Benjamin
> Bentmann|http://mail-archives.apache.org/mod_mbox/maven-dev/201105.mbox/%3c4dc87d9e.5010...@udo.edu%3E],
> Maven end users are currently limited in the control they have over the
> execution order of plugins bound to the same build phase unless they author
> their own custom Lifecycle and use a custom Package Type.
> While Maven is intended to be declarative rather than procedural and to do
> most of its work based on sensible defaults, it is a basic requirement of any
> build system to allow the end user to control the order in which actions
> occur and to do so with a minimum of effort.
> It should be possible to configure a plugin, simply and entirely within the
> POM, such that it will execute before, or even between, plugins defined by
> the lifecycle mappings.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
