[
https://issues.apache.org/struts/browse/STR-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niall Pemberton updated STR-3144:
---------------------------------
Affects Version/s: (was: 1.2.9)
(was: 1.2.8)
(was: 1.2.7)
This doesn't affect Struts1.2.x, so removing those versions - see
http://struts.apache.org/1.2.9/userGuide/struts-bean.html for example.
Since Struts 1.3.x and the move to m2 the documentation is generated using the
maven-taglib-plugin:
http://maven-taglib.sourceforge.net/m2/
The version of the maven-taglib-plugin is configured in the parent pom:
http://svn.apache.org/repos/asf/struts/struts1/trunk/pom.xml
...and the plugin is configured in the the component poms, e.g.:
http://svn.apache.org/repos/asf/struts/struts1/trunk/taglib/pom.xml
and the TLD files used by the plugin:
http://svn.apache.org/repos/asf/struts/struts1/trunk/taglib/src/main/resources/META-INF/tld/
I guess the HTML markup is a leftover from Struts 1.2.x and it looks like that
plugin doesn't handle it. Perhaps it should be removed, although that would be
a shame since it helped readability in Struts 1.2.x
> 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
>
> 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.
