You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Daniel Zardi Fernandes (JIRA)" <ji...@codehaus.org> on 2010/04/12 00:56:13 UTC
[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-tabpanel&focusedCommentId=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}
<xrefLocation>target/site/xref</xrefLocation>
<testXrefLocation>target/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}
<xrefLocation>target/site/xref</xrefLocation>
<testXrefLocation>target/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