[jira] (MPIR-35) Site Plugin should work from Template. Plugin Should not generate Markup from Java
[ https://jira.codehaus.org/browse/MPIR-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPIR-35. -- Resolution: Won't Fix Cleanup, reopen if you still care. > Site Plugin should work from Template. Plugin Should not generate Markup > from Java > --- > > Key: MPIR-35 > URL: https://jira.codehaus.org/browse/MPIR-35 > Project: Maven Project Info Reports Plugin > Issue Type: New Feature >Reporter: Tim O'Brien > 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 was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPIR-35) Site Plugin should work from Template. Plugin Should not generate Markup from Java
[ https://jira.codehaus.org/browse/MPIR-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MPIR-35: --- Fix Version/s: (was: 2.x) > Site Plugin should work from Template. Plugin Should not generate Markup > from Java > --- > > Key: MPIR-35 > URL: https://jira.codehaus.org/browse/MPIR-35 > Project: Maven Project Info Reports Plugin > Issue Type: New Feature >Reporter: Tim O'Brien > 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 was sent by Atlassian JIRA (v6.1.6#6162)
