[jira] Updated: (MPIR-35) Site Plugin should work from Template. Plugin Should not generate Markup from Java

["Adam Leggett (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MPIR-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam Leggett updated MPIR-35:
-----------------------------

    Attachment: project-info-itest.zip
                maven-project-info-reports.patch

Added a prospective patch to workaround the default vanilla text issue for project reports.

Solution is to allow a project to override the default properties file containing the messages for the reports.
I've made a change to AbstractProjectInfoReport to include an additional optional configuration element of <reportPropertiesBasename> that defaults to 'project-info-report'.
I've then done a prototype implementation  in the TeamListReport subclass and updated the corresponding Test Case.

Also attached some sample integration test projects - one that packages the property resource, which is then referenced as a dependency by the other project in the maven-project-info-reports-plugin configuration.

If the solution is deemed appropriate, i could modify the other report subclasses and make the testing more robust.

TIA

Adam

> Site Plugin should work from Template.  Plugin Should not generate Markup from Java
> -----------------------------------------------------------------------------------
>
>                 Key: MPIR-35
>                 URL: http://jira.codehaus.org/browse/MPIR-35
>             Project: Maven 2.x Project Info Reports Plugin
>          Issue Type: New Feature
>            Reporter: Tim O'Brien
>             Fix For: 2.2
>
>         Attachments: maven-project-info-reports.patch, project-info-itest.zip
>
>
> The site plugin currently generates markup from Java.  There is logic in the team list report that prints HTML and Javascript directly to a StringBuffer and there is no facility for customization.  Because of this, every single site that uses the project info reports ends up with the same text.  Google for the text of the team-list plugin and there are at least 18,000 matching pages.
> There needs to be a facility for customization.  I propose that the default report is published from a velocity template loaded form the classpath, but the site plugin checks for the presence of an overriding velocity template in a know path (or from a URL).

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