You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Danilo Eiji Seki (JIRA)" <ji...@codehaus.org> on 2008/02/12 21:24:30 UTC

[jira] Commented: (MSITE-188) Execution order of report plugins is arbitrary if inheritance is involved

    [ http://jira.codehaus.org/browse/MSITE-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_123441 ] 

Danilo Eiji Seki commented on MSITE-188:
----------------------------------------

I noticed something strange and made a test. I suspected plugins/reports were being executed in *alphabetic order* (first by groupId, then by artifactId) and so they are!

For example, I have a problem generating QALab reports in child projects, because QALab plugin was always executed before the reports that generate data. Then I noticed the reports were generated *almost* in the order I specify them (I use the above alphabetic order, expept for the QALab plugin, that is the last one). Then I imagined that maybe that happens because all my reports are from {{org.*}} groups while QALab belongs to {{net.*}}.

I tested it by creating a dummy plugin by renaming the groupId of a QALab report plugin to {{zzz.net.objectlab}} and deploying it to my local repository. Then I changed my root dependency to this new one and magic, *IT WORKS*.

I suspect someone is using a sorted collection (tree set, etc). Some display-beautifuly-list is messing things up.

> Execution order of report plugins is arbitrary if inheritance is involved
> -------------------------------------------------------------------------
>
>                 Key: MSITE-188
>                 URL: http://jira.codehaus.org/browse/MSITE-188
>             Project: Maven 2.x Site Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0-beta-4
>         Environment: maven 2.0.4, windows 2000
>            Reporter: David Vicente
>            Priority: Critical
>
> I have created a maven 2 report : Dashboard report which aggregate all reports results in one report.
> My plugin must be executed as the last one even if i can't bind the "post-site" phase or use the "aggregator" annotation.
> I declare my report plugin as the last one in the reporting section of my POM.
> When i run  mvn site on a single project, it's ok, my plugin has been executed as the last one.
> The reports list has been ordered as declared in my  POM.
> But if i run "mvn site" on a multi-project POM, the reports list isn't ordered as before.
> I think, it's the same problem as http://jira.codehaus.org/browse/MNG-1994?page=all

-- 
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