[jira] Issue Comment Edited: (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 edited comment on MNG-2258 at 4/11/10 5:54 PM:
--
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 and got the Taglist plugin MUST be executed
after the JXR plugin. message too.
was (Author: zardi):
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] Issue Comment Edited: (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 edited comment on MNG-2258 at 12/2/09 10:39 AM:
-
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
...
[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.
was (Author: henryju):
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] Issue Comment Edited: (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 edited comment on MNG-2258 at 8/27/09 9:17 AM:
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)
...
additional info:
it worked ok with 2.0.8 , but not since 2.0.9
was (Author: roti):
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
