You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Dave Newton (JIRA)" <ji...@apache.org> on 2007/09/17 23:00:36 UTC

[jira] Created: (WW-2190) Remove escapeAmp from struts-tags.tld to avoid documentation generation.

Remove escapeAmp from struts-tags.tld to avoid documentation generation.
------------------------------------------------------------------------

                 Key: WW-2190
                 URL: https://issues.apache.org/struts/browse/WW-2190
             Project: Struts 2
          Issue Type: Bug
          Components: Views
            Reporter: Dave Newton
            Priority: Trivial


The escapeAmp documentation is showing up in the tag reference.

There seems to have been some confusion about whether or not this parameter should exist. In trunk (as of 17 Sep 2007) the tag partially exists in the TLD but with no name element; what will the final resolution be?


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


[jira] Closed: (WW-2190) Remove escapeAmp from struts-tags.tld to avoid documentation generation.

Posted by "James Holmes (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/struts/browse/WW-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Holmes closed WW-2190.
----------------------------

    Resolution: Not A Problem

The problem here is that the live Wikie docs reference the code in Subversion. In Struts 2.0.10 there are changed to the URL tag that add the "escapeAmp" attribute. That is why you see that attribute if you go to:

http://cwiki.apache.org/confluence/display/WW/url

However, if you go to the docs for Struts 2.0.9 you will not see anything about the "escapeAmp" attribute.

http://struts.apache.org/2.0.9/docs/url.html

Unfortunately this is a side effect of how the Struts 2 docs are set up and I don't believe there's a current solution to the problem. Not to say that we couldn't come up with one...

I'm going to close this as Not A Problem.

> Remove escapeAmp from struts-tags.tld to avoid documentation generation.
> ------------------------------------------------------------------------
>
>                 Key: WW-2190
>                 URL: https://issues.apache.org/struts/browse/WW-2190
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Views
>            Reporter: Dave Newton
>            Priority: Trivial
>             Fix For: 2.0.11
>
>
> The escapeAmp documentation is showing up in the tag reference.
> There seems to have been some confusion about whether or not this parameter should exist. In trunk (as of 17 Sep 2007) the tag partially exists in the TLD but with no name element; what will the final resolution be?

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


[jira] Updated: (WW-2190) Remove escapeAmp from struts-tags.tld to avoid documentation generation.

Posted by "James Holmes (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/struts/browse/WW-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Holmes updated WW-2190:
-----------------------------

    Fix Version/s: 2.0.11

> Remove escapeAmp from struts-tags.tld to avoid documentation generation.
> ------------------------------------------------------------------------
>
>                 Key: WW-2190
>                 URL: https://issues.apache.org/struts/browse/WW-2190
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Views
>            Reporter: Dave Newton
>            Priority: Trivial
>             Fix For: 2.0.11
>
>
> The escapeAmp documentation is showing up in the tag reference.
> There seems to have been some confusion about whether or not this parameter should exist. In trunk (as of 17 Sep 2007) the tag partially exists in the TLD but with no name element; what will the final resolution be?

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