You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Wendy Smoak (JIRA)" <ji...@codehaus.org> on 2011/05/08 14:24:22 UTC

[jira] Commented: (MNG-5088) The order of plugins within the same phase cannot be specified in Maven 3

    [ http://jira.codehaus.org/browse/MNG-5088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=266001#action_266001 ] 

Wendy Smoak commented on MNG-5088:
----------------------------------

A better way to get it some attention would be to bring it up on the mailing list, not open a bug report that you already know is going to get closed as a duplicate...



> The order of plugins within the same phase cannot be specified in Maven 3
> -------------------------------------------------------------------------
>
>                 Key: MNG-5088
>                 URL: http://jira.codehaus.org/browse/MNG-5088
>             Project: Maven 2 & 3
>          Issue Type: Bug
>    Affects Versions: 3.0.3
>         Environment: Windows
>            Reporter: Graham Lea
>         Attachments: build.log, pom.xml
>
>
> This report is a duplicate of MNG-2258, HOWEVER it seems no one is paying attention to that issue as it is a Blocker Bug but it has been around for 5 years now and is still not assigned to anyone. I realise it's poor form to create a duplicate bug, and I apologise, but it seemed to me that adding a comment to an issue that's been ignored for 5 years would probably not have any effect.
> The problem is simple: people need the ability to control the order in which plugins within the same phase are executed. At the moment this appears not to be possible, at least in Maven 3.0.3 - the latest and greatest, right?
> I am attaching a simple pom which, when executed with 'mvn install', executes the plugins in the opposite order to what is specified in the pom (on my machine, at least). No other source files are necessary for reproducing the problem.
> Also attached is the -X output of running the build.
> It's my understanding that someone submitted a patch or at least suggested a simple solution on the older issue, MNG-2258.
> I don't mind if this issue is closed as a duplicate, as long as someone is assigned to look at MNG-2258.
> Thanks.

-- 
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