commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simone Tripodi (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FUNCTOR-18) [PATCH] Fix duplicated entries in examples page of [functor] website, and replace <br/> tags in aggregator.xml
Date Fri, 01 Jun 2012 12:57:23 GMT

     [ https://issues.apache.org/jira/browse/FUNCTOR-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Simone Tripodi resolved FUNCTOR-18.
-----------------------------------

    Resolution: Fixed
      Assignee: Simone Tripodi

fixed on r1345145

thanks again Bruno! :)
                
> [PATCH] Fix duplicated entries in examples page of [functor] website, and replace <br/>
tags in aggregator.xml
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: FUNCTOR-18
>                 URL: https://issues.apache.org/jira/browse/FUNCTOR-18
>             Project: Commons Functor
>          Issue Type: Bug
>            Reporter: Bruno P. Kinoshita
>            Assignee: Simone Tripodi
>            Priority: Minor
>              Labels: duplicate, html, site
>         Attachments: FUNCTOR-18.patch
>
>
> Hello, 
> There is some duplication in examples.xml. It happened due to two patches that modified
the same file. 
> There are also <br/> tags where there is a standard for <p>. This causes
the rendered web page to display some pages or parts of the pages differently.
> The file aggregate.xml is not being referenced. It had been renamed to aggregator.xml
(the link the examples.html is pointing to aggregator.html). So I believe there is no problem
in removing this file.
> The proposed patch in this issue:
> - updates examples.xml, removing the duplicated entries, but keeps the aggregator new
section.
> - replaces all the <br/> tags present in examples.xml and aggregator.xml by <p>
tags.
> - removes aggregate.xml file
> Thank you in advance!
> Bruno

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message