[jira] Resolved: (STR-3144) Bean Taglib Documentation Has Been Unreadable FOR YEARS...

["Niall Pemberton (JIRA)" <ji...@apache.org>]

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

Niall Pemberton resolved STR-3144.
----------------------------------

    Resolution: Fixed
      Assignee: Niall Pemberton  (was: Paul Benedict)

Fixed http://svn.apache.org/viewvc?view=rev&revision=657352

The problem was that the version and parseHtml parameter are specified in the build/pluginManagement section in the struts-parent parent pom, but the <reporting> element doesn't take any noitce of that, setting the version and parseHtml in the plugin config in each pom resolves it.

I'm uploading a new version of the 1.x site for the modules affected - and will re-generate the tagreference pages for 1.3.8 and 1.3.9 shortly

> Bean Taglib Documentation Has Been Unreadable FOR YEARS...
> ----------------------------------------------------------
>
>                 Key: STR-3144
>                 URL: https://issues.apache.org/struts/browse/STR-3144
>             Project: Struts 1
>          Issue Type: Bug
>          Components: Taglibs
>    Affects Versions: 1.3.0, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.3.6, 1.3.7, 1.3.8, 1.3.9
>         Environment: Any OS, any browser.
>            Reporter: Daniel A. Torrey
>            Assignee: Niall Pemberton
>             Fix For: 1.3.10
>
>         Attachments: struts1-taglib-pom.diff
>
>
> The page http://struts.apache.org/1.3.8/struts-taglib/tagreference.html has been unreadable for YEARS.  The output has all of the markup tags escaped, so instead of rendering a paragraph tag as the end of a paragraph, the literal string "<p>" is written.  This makes the documentation worth very little.
> The last time I worked on a Struts app, in May of 2007, this was the case.
> The time before that that I worked on a Struts app, in October of 2006, this was the case.
> I've never reported it, as I've always thought that a) someone would fix it and b) you must have already been flooded by reports.  Or maybe nobody in the world except me actually reads documentation?
> This really should be fixed - it reflects very poorly on the development / documentation team.  I'd be glad to help, but I wouldn't have a clue where to start.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.