[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-tabpanelfocusedCommentId=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] 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-tabpanelfocusedCommentId=270991#comment-270991 ] Benson Margulies commented on MNG-2258: --- I ran the test case and it executed in the right order with 3.0.3. I don't know what to suggest if that's not happening for you. 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] Commented: (MNG-2258) Wrong execution order of plugins in same phase
[ http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=227561#action_227561 ] Benjamin Bentmann commented on MNG-2258: I just got aware of the fact that inheritance (and probably profile injection) has a rather counterintuitive effect on the plugin order in the POM. The plugin order given by a parent POM is dominant over the plugin order in a child POM. This circumstance might add to the observation that the POM order (as given in the current child project) is not respected. Wrong execution order of plugins in same phase -- Key: MNG-2258 URL: http://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 Priority: Blocker 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. - 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
[ http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=225995#action_225995 ] Laird Nelson commented on MNG-2258: --- This bug is still present in Maven 2.2.1. My project runs a goal from maven-dependency-plugin, maven-resources-plugin and maven-jar-plugin during the prepare-package phase. These are listed in that order. They are executed in an arbitrary order. Wrong execution order of plugins in same phase -- Key: MNG-2258 URL: http://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 Priority: Blocker 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. - 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
[ http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=221919#action_221919 ] Sebastian Paul commented on MNG-2258: - @Daniel: How did you work around this issue without running jxr twice? I am using Maven 2.2.1 too, and have the same issue. When jxr only runs once in pre-site, the report does not contain a link to the source (Reports section in the navigation area). Only the tag list plugin correctly links to the source... Wrong execution order of plugins in same phase -- Key: MNG-2258 URL: http://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 Priority: Blocker 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. - 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
[
http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=217593#action_217593
]
Daniel Zardi Fernandes commented on MNG-2258:
-
I found this bug while looking for a solution to the taglist-maven-plugin issue
with the maven-jxr-plugin, so I have no knowledge about the execution order
bug, but I managed to get the taglist plugin working without a second run of
jxr.
I noticed that when running jxr in the pre-site phase the output where
generated in the reports directory, not in the site directory, so it's probably
an issue of the taglist-maven-plugin.
Try adding the following to the taglist-maven-plugin configuration, it worked
for me (don't forget to change the directories to match your configuration if
needed).
{code:xml}
xrefLocationtarget/site/xref/xrefLocation
testXrefLocationtarget/site/xref-test/testXrefLocation
{code}
Probably it won't help with this bug, but it's a better workaround than running
jxr twice.
By the way, I'm using Maven 2.2.1 too and got the Taglist plugin MUST be
executed after the JXR plugin. message too.
Wrong execution order of plugins in same phase
--
Key: MNG-2258
URL: http://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
Priority: Blocker
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.
-
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
[ http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=205140#action_205140 ] wargre commented on MNG-2258: - funny thing is adding an execution in pre-site made another reporting plugin ordering. Wrong execution order of plugins in same phase -- Key: MNG-2258 URL: http://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 Priority: Blocker 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. - 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
[ http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=204734#action_204734 ] wargre commented on MNG-2258: - Hi, i've got same issue as Julien with 2.2.1 version. Does anyone have a workaround? Wrong execution order of plugins in same phase -- Key: MNG-2258 URL: http://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 Priority: Blocker 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. - 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
[
http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=204741#action_204741
]
Pablo commented on MNG-2258:
@wargre: My workaround is to run JXR twice:
* first time in the pre-site phase (with the POM snippet below), so you're sure
it's done before the rest.
* second time in the standard reporting section, so you get the XREF links in
the site menu.
{code}
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jxr-plugin/artifactId
executions
execution
idjxr-pre-site/id
phasepre-site/phase
goals
goaljxr/goal
goaltest-jxr/goal
/goals
/execution
/executions
/plugin
/plugins
/build
{code}
Wrong execution order of plugins in same phase
--
Key: MNG-2258
URL: http://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
Priority: Blocker
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.
-
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
[
http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200327#action_200327
]
Julien HENRY commented on MNG-2258:
---
In my corporate parent pom I have the following in reporting section:
{code:xml}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jxr-plugin/artifactId
version2.1/version
/plugin
...
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdtaglist-maven-plugin/artifactId
version2.4/version
/plugin
{code}
(in this order)
Then I have create a sample test project from Maven quickstart archetype but:
{noformat}
mvn clean install site dependency:tree
...
[INFO] Generating Tag List report.
[ERROR] Taglist plugin MUST be executed after the JXR plugin. No links to xref
were generated.
[WARNING] Unable to locate Source XRef to link to - DISABLED
{noformat}
Looking at the log I can see reporting plugins are generated in an order
completely different of the reporting section order.
Wrong execution order of plugins in same phase
--
Key: MNG-2258
URL: http://jira.codehaus.org/browse/MNG-2258
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.0.4
Environment: N/A
Reporter: David J. M. Karlsen
Priority: Blocker
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.
-
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
[ http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200336#action_200336 ] Martin Zeltner commented on MNG-2258: - Hi Julien Are you sure that you're using Maven 2.2.1, the newest one? All previous version where for trash, when you where going into details, like the execution order in one phase. Also the current version needs still some fine tuning, that I'm currently working out. Cheers Martin Wrong execution order of plugins in same phase -- Key: MNG-2258 URL: http://jira.codehaus.org/browse/MNG-2258 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.4 Environment: N/A Reporter: David J. M. Karlsen Priority: Blocker 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. - 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
[
http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=188803#action_188803
]
Hrotkó Gábor commented on MNG-2258:
---
I am not a big maven guru, but we have this problem now with 2.2.1
My breaf description is this:
the first transitive dependency version will win
{code:xml}
...
dependency !-- has a dependency on myModul_X-1.0 --
groupIdmyCompany.myType/groupId
artifactIdmyModul_B/artifactId
version1.0/version
typemyType/type
/dependency
dependency !-- has a dependency on myModul_X-1.2 --
groupIdmyCompany.myType/groupId
artifactIdmyModul_A/artifactId
version1.0/version
typemyType/type
/dependency
...
{code}
after the build, myModul_X-1.0 will be included
...
[DEBUG] myCompany.myType:myModul_A:myType:1.0:compile (selected for compile)
[DEBUG] myCompany.myType:myModul_X:myType:1.2:compile (removed - nearer
found: 1.0)
...
but when myModul_A is the first in the pom:
{code:xml}
...
dependency !-- has a dependency on myModul_X-1.2 --
groupIdmyCompany.myType/groupId
artifactIdmyModul_A/artifactId
version1.0/version
typemyType/type
/dependency
dependency !-- has a dependency on myModul_X-1.0 --
groupIdmyCompany.myType/groupId
artifactIdmyModul_B/artifactId
version1.0/version
typemyType/type
/dependency
...
{code}
after the build, myModul_X-1.2 will be included
...
[DEBUG] myCompany.myType:myModul_X:myType:1.0:compile (removed - nearer
found: 1.2)
...
Wrong execution order of plugins in same phase
--
Key: MNG-2258
URL: http://jira.codehaus.org/browse/MNG-2258
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.0.4
Environment: N/A
Reporter: David J. M. Karlsen
Priority: Blocker
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.
-
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
[
http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=188804#action_188804
]
Benjamin Bentmann commented on MNG-2258:
Hrotkó, the dependency resolution works as designed, cf. [Introduction to the
Dependency
Mechanism|http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Transitive_Dependencies].
If you don't want to rely on the nearest-/first-wins strategy for conflict
resolution, you can use {{dependencyManagement}} to control the versions of
the transitive dependencies.
Wrong execution order of plugins in same phase
--
Key: MNG-2258
URL: http://jira.codehaus.org/browse/MNG-2258
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.0.4
Environment: N/A
Reporter: David J. M. Karlsen
Priority: Blocker
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.
-
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
[ http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=187475#action_187475 ] E K commented on MNG-2258: -- Maven is grouping executions of same plugin at same phase without checking whether there is/are execution(s) of another plugin(s) in between or not in the pom file. And this cause the execution order specified by Jayesh Lalwani. A dummy project is attached if it is necessary to see the problem. Suggested solution by John Casey on MNG-3719 is to use different phases for execution of same plug-in. Is this going to be fixed or should we follow suggested cheating ? Wrong execution order of plugins in same phase -- Key: MNG-2258 URL: http://jira.codehaus.org/browse/MNG-2258 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.4 Environment: N/A Reporter: David J. M. Karlsen Priority: Blocker 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. - 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
[ http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=187501#action_187501 ] John Casey commented on MNG-2258: - Re-specifying the same plugin in two different XML blocks of the build section within the same POM (without using profiles) is NOT valid. This is a recipe for disaster. If users must replicate any new configurations across multiple plugin sections just to get consistent behavior for all mojos in a plugin, this will cause massive confusion. I do agree that we should detect this scenario and fail with a validation error, so I'm not going to close this issue yet. But if you want two mojo executions from the same plugin to happen before and after another mojo from another plugin, you must assign them to different phases to arrange this. Wrong execution order of plugins in same phase -- Key: MNG-2258 URL: http://jira.codehaus.org/browse/MNG-2258 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.4 Environment: N/A Reporter: David J. M. Karlsen Priority: Blocker 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. - 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
[ http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=183906#action_183906 ] Benjamin Bentmann commented on MNG-2258: Could one of the reporters attach a working example POM to reproduce this? Wrong execution order of plugins in same phase -- Key: MNG-2258 URL: http://jira.codehaus.org/browse/MNG-2258 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.4 Environment: N/A Reporter: David J. M. Karlsen Priority: Blocker 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. - 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
[ http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=183762#action_183762 ] Justin K commented on MNG-2258: --- I Agree. This bug is not fixed in 2.2.0. Wrong execution order of plugins in same phase -- Key: MNG-2258 URL: http://jira.codehaus.org/browse/MNG-2258 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.4 Environment: N/A Reporter: David J. M. Karlsen Assignee: John Casey Priority: Blocker Fix For: 2.2.0 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. - 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
[ http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=183118#action_183118 ] Jayesh Lalwani commented on MNG-2258: - Just tried this issue in with 2.2 and doesn't look like it's fixed. The pom has a profile with 4 plugins in the following order a) SQL-maven plugin. This plugin drops the database b) hibernate3-maven-plugin :- this creates the database schema c) dbunit-maven-plugin: populates the data with some test data d) SQL-maven plugin:- Adds some more test data to the database All ther executions are tied to process-test-resources phase. Maven executes the plugins in order a, d, b, c, instead of a, b, c, d Wrong execution order of plugins in same phase -- Key: MNG-2258 URL: http://jira.codehaus.org/browse/MNG-2258 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.4 Environment: N/A Reporter: David J. M. Karlsen Assignee: John Casey Priority: Blocker Fix For: 2.2.0 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. - 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
[ http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=178662#action_178662 ] David Haccoun commented on MNG-2258: Hi, This bug is always present in the 2.1 version. On the state of this issue, we can see that is closed. The reason : Duplicate. But where is the reference of the duplicated issue ? Cheers, David Wrong execution order of plugins in same phase -- Key: MNG-2258 URL: http://jira.codehaus.org/browse/MNG-2258 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.4 Environment: N/A Reporter: David J. M. Karlsen Assignee: John Casey 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. - 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
[ http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=156957#action_156957 ] Sandra Bogaert commented on MNG-2258: - Hi, What about this issue ? Do you have a release date ? Thanks in advance Wrong execution order of plugins in same phase -- Key: MNG-2258 URL: http://jira.codehaus.org/browse/MNG-2258 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.4 Environment: N/A Reporter: David J. M. Karlsen Assignee: John Casey 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. - 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
[ http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125804 ] Andrew Robinson commented on MNG-2258: -- This is a blocking issue, why is it being left to 2.1? Wrong execution order of plugins in same phase -- Key: MNG-2258 URL: http://jira.codehaus.org/browse/MNG-2258 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.4 Environment: N/A Reporter: David J. M. Karlsen Assignee: John Casey Fix For: 2.1 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. - 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
[ http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113918 ] Viktor Nordling commented on MNG-2258: -- It seems that this issue is not actually resolved. The fix version is set to 2.1, but if I am not mistaken, 2.1 has not been released yet? Since we need this issue to be fixed for our project, I would be happy if it could be reopened. Wrong execution order of plugins in same phase -- Key: MNG-2258 URL: http://jira.codehaus.org/browse/MNG-2258 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.4 Environment: N/A Reporter: David J. M. Karlsen Assignee: John Casey Fix For: 2.1 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. - 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
[ http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96876 ] Sebastian Davids commented on MNG-2258: --- This bug should be solved independent of MNG-1412. This is a *serious* defect. Considering the high number of votes and watchers it is important to a lot of people. It should be backported to 2.0.x stream. After that a new 2.0.x release should be made. Having to wait over one year for a simple HashSet - LinkedHashSet and HashMap - LinkedHashMap replacement is ridiculous. Even more so, considering that a patch has been supplied over half a year ago. @@ Use Case @@ project ... ... modules moduleejb/module modulewar/module /modules ... build ... plugins plugin artifactIdmaven-antrun-plugin/artifactId inheritedfalse/inherited executions execution phaseinstall/phase configuration tasks ... deploy to server ... /tasks /configuration goals goalrun/goal /goals /execution /executions /plugin /plugins ... /build ... /project Let's say ejb contains EJB stuff and war contains the web application; war depends on ejb; and both are children of a parent POM, so that the generated ejb JAR gets packaged into the WAR. Now we want to be able to use install to deploy the created WAR to the server (yes, there's Cargo, but it does not support all JEE containers, yet.) We have to set inheritedfalse/inherited so Maven won't run the deployment for ejb and war. But it does not work because maven-antrun-plugin is run before the children (ejb and war) are run. Wrong execution order of plugins in same phase -- Key: MNG-2258 URL: http://jira.codehaus.org/browse/MNG-2258 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.4 Environment: N/A Reporter: David J. M. Karlsen Fix For: 2.1.x 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. - 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
[ http://jira.codehaus.org/browse/MNG-2258?page=comments#action_78375 ] Martin Zeltner commented on MNG-2258: - BTW the patches appended to MNG-1412 does also solve the execution order problem of plugins. It does solve the order problem for all artifacts! Until today the HashSets and HashMaps where not replaced by LinkedHashSets and LinkedHashMaps (see SVN repo). I don't understand why commiters from these Maven 2 components don't apply the patches for such an important issue. I would help if I had commit rights but right now i can just watch and claim. Cheers, Martin http://el4j.sf.net Wrong execution order of plugins in same phase -- Key: MNG-2258 URL: http://jira.codehaus.org/browse/MNG-2258 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.4 Environment: N/A Reporter: David J. M. Karlsen Fix For: 2.1 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. - 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
[ http://jira.codehaus.org/browse/MNG-2258?page=comments#action_78361 ] Brian Topping commented on MNG-2258: Same problem here. It's possible to make a new goal on a mojo so that one contains another, but there's no other way to get them to cleanly execute in order. Wrong execution order of plugins in same phase -- Key: MNG-2258 URL: http://jira.codehaus.org/browse/MNG-2258 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.4 Environment: N/A Reporter: David J. M. Karlsen Fix For: 2.1 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. - 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
[ http://jira.codehaus.org/browse/MNG-2258?page=comments#action_70136 ] Martin Zeltner commented on MNG-2258: - I'd rate this issue much higher too. I've already solved the order problem with dependencies (see MNG-1412) and this issue can be solved equivalently. Wrong execution order of plugins in same phase -- Key: MNG-2258 URL: http://jira.codehaus.org/browse/MNG-2258 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.4 Environment: N/A Reporter: David J. M. Karlsen Fix For: 2.1 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. - 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
[ http://jira.codehaus.org/browse/MNG-2258?page=comments#action_70086 ] David Hay commented on MNG-2258: I'd actually rate this much higher priority. I've already run into this limitation several times during the development of my project. In particular, I want to run the dependency-maven-plugin:copy followed by the assembly plugin. But maven wants to run them in the opposite order, which doesn't work very well. I've also wanted to run the hibernate3-plugin to generate my DDL followed by an antrun plugin to load some sample data, but I can't be assured that the plugins will run in that order. Wrong execution order of plugins in same phase -- Key: MNG-2258 URL: http://jira.codehaus.org/browse/MNG-2258 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.4 Environment: N/A Reporter: David J. M. Karlsen Fix For: 2.1 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. - 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
[ http://jira.codehaus.org/browse/MNG-2258?page=comments#action_65019 ] Fredrik Vraalsen commented on MNG-2258: --- I'm having the same problem. I need to run two plugins in the generate-sources phase, where one depends on the output of the other. For more information, please see http://www.nabble.com/Plugin-execution-order-within-lifecycle-phase-t1541372.html#a4187121 Wrong execution order of plugins in same phase -- Key: MNG-2258 URL: http://jira.codehaus.org/browse/MNG-2258 Project: Maven 2 Type: Bug Versions: 2.0.4 Environment: N/A Reporter: David J. M. Karlsen 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. - 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
