[jira] Created: (MNG-5088) The order of plugins within the same phase cannot be specified in Maven 3
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
[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=266025#action_266025 ] Graham Lea commented on MNG-5088: - Thanks for the advice, Wendy. Will do. > 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
[jira] Created: (MNG-5090) Maven End Users should be able to control the execution order of plugins without creating a custom Lifecycle and Package Type
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: http://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 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 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
[jira] Commented: (MNG-2258) Wrong execution order of plugins in same phase
[ https://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=270973#comment-270973 ] Graham Lea commented on MNG-2258: - Please consider reviewing MNG-3522 and MNG-5090 as examples of distinct JIRAs with test cases that are not resovled in 3.0.3. > Wrong execution order of plugins in same phase > -- > > Key: MNG-2258 > URL: https://jira.codehaus.org/browse/MNG-2258 > Project: Maven 2 & 3 > Issue Type: Bug >Affects Versions: 2.0.4 > Environment: N/A >Reporter: David J. M. Karlsen >Assignee: Benson Margulies >Priority: Blocker > Fix For: 3.0.3 > > Attachments: mavenTest.zip > > > AFAIK plugins should be execute in the same order as they are listed in the > POM, when bound to the same phase. This does not happen, the execution order > is arbitrary. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1014) Upload Simple Log 2.0.1
Upload Simple Log 2.0.1 --- Key: MAVENUPLOAD-1014 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1014 Project: maven-upload-requests Issue Type: Task Reporter: Graham Lea https://simple-log.dev.java.net/mavenUpload/maven-simple-log.jar https://simple-log.dev.java.net/mavenUpload/maven-simple-log-rollover.jar https://simple-log.dev.java.net/mavenUpload/maven-simple-log-slf4j.jar https://simple-log.dev.java.net/mavenUpload/maven-simple-log-commons-logging.jar https://simple-log.dev.java.net/ https://simple-log.dev.java.net/nonav/userGuide/faq.html Simple Log is a logging anti-framework. Simple Log 1.7 is already on ibiblio, though was uploaded by one of its users, not by the developer. 2.0.1 is the first release of 2.0 to be uploaded to Maven. -- 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
[jira] Created: (MAVENUPLOAD-1762) Joda Time 2007h upload
Joda Time 2007h upload -- Key: MAVENUPLOAD-1762 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1762 Project: maven-upload-requests Issue Type: Task Reporter: Graham Lea http://www.grlea.org/joda-time-1.4-tz2007h-maven.jar http://joda-time.sourceforge.net This is just version 1.4 of Joda Time built with the 2007h version of the public timezone database, using the instructions at http://joda-time.sourceforge.net/tz_update.html -- 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
[jira] Commented: (SUREFIRE-257) surefire-report reruns tests
[ http://jira.codehaus.org/browse/SUREFIRE-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88106 ] Graham Lea commented on SUREFIRE-257: - Regardless of whether this is the best solution or not, it contains the functionality that most people want. Please commit it to the Maven repository so we can use it. > surefire-report reruns tests > > > Key: SUREFIRE-257 > URL: http://jira.codehaus.org/browse/SUREFIRE-257 > Project: Maven Surefire > Issue Type: Bug > Components: report plugin > Environment: maven 2.0 >Reporter: Dirk Sturzebecher > Fix For: 2.3 > > Attachments: MSUREFIREREP-6-patch.txt > > > surefire-report reruns the tests. In my case this is not just annoying, but > leads to a failure, as the VM (probably) is reused and leftovers from the > first tests are (definitly) still present. > I run maven with: clean package site -- 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
