yes, i think that all internal process in
org.apache.maven.plugins.site.AbstractSiteRenderingMojo class to configure
the model and the renderer must be pushed in doxia.
With this, when Maven set the siteRenderer component in the report Mojo, the
sink object used by the report is well configured.
it will be compatible with Maven older versions ?
brettporter wrote:
>
> You're right - sorry, I was misremembering. I did add enough to bring
> in the default skin, but not to read site.xml.
>
> What really needs to happen is for more of the site plugin to be
> pushed into the doxia-sitetools, so that they can then be used from
> the reporting implementation (as you say)
>
> - Brett
>
> On 27/08/2007, at 7:45 PM, dvicente wrote:
>
>>
>> Hi Brett,
>>
>> it doesn't work.
>>
>> i take a look to the source code and it creates a
>> SiteRenderingContext with
>> the default skin.
>>
>> if you make a test with a projet, with the sylus skin in site.xml as :
>> <?xml version="1.0" encoding="ISO-8859-1"?>
>> <project name="Maven">
>> <bannerLeft>
>> <name>${project.name}</name>
>> </bannerLeft>
>> <bannerRight>
>> <name></name>
>> </bannerRight>
>> <skin>
>> <groupId>org.apache.maven.skins</groupId>
>> <artifactId>maven-stylus-skin</artifactId>
>> <version>1.0.1</version>
>> </skin>
>> <body>
>> <links>
>> <item name="Maven 2" href="http://maven.apache.org/"/>
>> </links>
>> ${reports}
>> </body>
>> </project>
>>
>> if you launch a "mvn site" command, it works fine but when you
>> launch a "mvn
>> project-info-reports:project-team" command , for example, the
>> generated
>> report lost the left menu and the stylus skin is crushing by the
>> default one
>> :,(
>>
>> all reports generated by "mvn site" command are ok.
>>
>> But if you launch any report as standalone mvn command, you lost
>> the left
>> menu for this report and the specified skin for the whole site.
>>
>> i don't think it's a good idea that my report mojo extend the
>> org.apache.maven.plugins.site.AbstractSiteRenderingMojo class
>> instead of
>> AbstractMavenReport.
>>
>> i think that the org.codehaus.doxia.site.renderer.SiteRenderer
>> component
>> must be set by Maven with the right context or configuration
>>
>> brettporter wrote:
>>>
>>> Take a look at the project info reports plugin - I'm pretty sure that
>>> the execute() goal for those correctly obtains the details.
>>>
>>> Let me know if you have any trouble finding it and I can poke around
>>> and find the exact code.
>>>
>>> Cheers,
>>> Brett
>>>
>>> On 24/08/2007, at 6:19 PM, dvicente wrote:
>>>
>>>>
>>>> Hi,
>>>>
>>>> I will explain my problem :
>>>>
>>>> when i run a "mvn site" command, The site plugin generates the menu
>>>> on the
>>>> left and applies the good skin (the default one if not specified in
>>>> site.xml
>>>> or that specified) for each generated report.
>>>>
>>>> When the dashboard plugin is executed during the phase site, I have
>>>> all that
>>>> well but my report is empty, considering this one requires that the
>>>> others
>>>> are generated to aggregate datas but that it is normal.
>>>>
>>>> Thus to fill my Dashboard report, I am obliged to run a "mvn
>>>> dashboard-reportd:dashboard" after the "mvn site" execution.
>>>>
>>>> There, my report is well filled but I lose the menu and the skin
>>>> (that in
>>>> target \ site is crushed by the default), which seems normal.
>>>>
>>>> Now my question is:
>>>>
>>>> how, in a simple way, I can, in my plugin, recover a
>>>> “RenderContext” with
>>>> identical of that set up by the site plugin, which, when I use the
>>>> sink to
>>>> fill my report, already enables me to have the built left menu and
>>>> especially that the execution of my report does not crush the
>>>> selected skin
>>>> set up in site.xml by the default one?
>>>>
>>>> --
>>>> View this message in context: http://www.nabble.com/Maven-report-
>>>> and-site-render-context-tf4322290s177.html#a12308388
>>>> Sent from the Maven Developers mailing list archive at Nabble.com.
>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> -
>>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>>
>>
>> --
>> View this message in context: http://www.nabble.com/Maven-report-
>> and-site-render-context-tf4322290s177.html#a12344190
>> Sent from the Maven Developers mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/Maven-report-and-site-render-context-tf4322290s177.html#a12363913
Sent from the Maven Developers mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
