Hi,

yes it's a known problem but it's a generic problem with the site plugin.

see :  http://jira.codehaus.org/browse/MOJO-872
http://jira.codehaus.org/browse/MOJO-872 
or
http://jira.codehaus.org/browse/MOJO-700
http://jira.codehaus.org/browse/MOJO-700 

the problem is , for every plugin report :

when you run "mvn site", the site plugin create a rendering context, et
invoke each report plugin with it
and all works fine.

But if you run a single report as dashboard ( or pmd for example ) , this
context is lost and you have not the left menu or the correct skin in your
report.
You can make a try with pmd

- run "mvn site" and look the pmd report, all works fine
- after, run "mvn pmd:pmd" and look the pmd report, you lost all navigation
link.

It's a general problem for all maven report plugin.

I hope that it will be corrected with the 2.0-beta-6 maven-site-plugin




GisbertAmm wrote:
> 
> Ah yes, dashboard-report-historic.html is there and looks fine. Never
> mind.
> 
> Another question: Is there any documentation how to integrate this report
> into the navigation of the project site? ATM there's no link to it and
> itself does not have the navigation apart from a link named "Root" that
> leads back to the project site.
> 
> Thanks for your help.
> -Gisbert
> 
> 
> dvicente wrote:
>> 
>> I don't understand, this piece of code is not the dashboard HTML result.
>> 
>> The correct file of historic page which is generated by dashboard is :
>> /target/site/dashboard-report-historic.html
>> 
>> the correct URL to JIRA is :  http://jira.codehaus.org/browse/MOJO
>> http://jira.codehaus.org/browse/MOJO 
>> 
>> and the "dashboard" component exist under this section.
>> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Maven-Dashboard-Plugin%3A-History-Report-wrong-tf4574165.html#a13057273
Sent from the mojo - user mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply via email to