[ 
http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-jxr-plugin</artifactId>
      <executions>
        <execution>
          <id>jxr-pre-site</id>
          <phase>pre-site</phase>
          <goals>
            <goal>jxr</goal>
            <goal>test-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

        

Reply via email to