You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Daniel A. Torrey (JIRA)" <ji...@apache.org> on 2008/05/14 16:48:05 UTC
[jira] Created: (STR-3144) Bean Taglib Documentation Has Been
Unreadable FOR YEARS...
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.9, 1.3.8, 1.3.7, 1.3.6, 1.3.5, 1.3.4, 1.3.3, 1.3.2, 1.3.1, 1.3.0, 1.2.9, 1.2.8, 1.2.7
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.
[jira] Commented: (STR-3144) Bean Taglib Documentation Has Been
Unreadable FOR YEARS...
Posted by "Niall Pemberton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/STR-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43877#action_43877 ]
Niall Pemberton commented on STR-3144:
--------------------------------------
I made the same mistake - even though I knew it - saw the version/parseHtml in struts-parent and forgot it didn't affect reporting.
Looks like the sites synced, and the new versions are now available:
http://struts.apache.org/1.x/struts-taglib/tagreference.html
http://struts.apache.org/1.3.9/struts-taglib/tagreference.html
http://struts.apache.org/1.3.8/struts-taglib/tagreference.html
(I also did el, faces and tiles tagreference.html)
> 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.
[jira] Resolved: (STR-3144) Bean Taglib Documentation Has Been
Unreadable FOR YEARS...
Posted by "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.
[jira] Commented: (STR-3144) Bean Taglib Documentation Has Been
Unreadable FOR YEARS...
Posted by "Paul Benedict (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/STR-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43861#action_43861 ]
Paul Benedict commented on STR-3144:
------------------------------------
Have you tried this solution yourself? The "parseHtml" flag does not affect escaping; it is only used for validating that the HTML is well-formed. I tried this solution myself many months ago and found no improvement. Please tell me if you have a different result.
> 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.
[jira] Updated: (STR-3144) Bean Taglib Documentation Has Been
Unreadable FOR YEARS...
Posted by "Paul Benedict (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/STR-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Benedict updated STR-3144:
-------------------------------
Fix Version/s: 1.3.10
Assignee: Paul Benedict
Great. Thanks.
> 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: Paul Benedict
> 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.
[jira] Commented: (STR-3144) Bean Taglib Documentation Has Been
Unreadable FOR YEARS...
Posted by "Niall Pemberton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/STR-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43888#action_43888 ]
Niall Pemberton commented on STR-3144:
--------------------------------------
Ported to 1.3 Branch:
http://svn.apache.org/viewvc?view=rev&revision=657483
> 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.
[jira] Commented: (STR-3144) Bean Taglib Documentation Has Been
Unreadable FOR YEARS...
Posted by "Matthieu Chase Heimer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/STR-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43856#action_43856 ]
Matthieu Chase Heimer commented on STR-3144:
--------------------------------------------
I just submitted patches for the same issue for the tile-jsp.tld tag reference page. See: https://issues.apache.org/struts/browse/TILES-274. As long as the latest taglib plugin is used there is a pom.xml configuration change that can be made to disable the escaping that is happening. You must be very careful to make the html in the description well formed and manually escape everything in any code blocks.
> 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.
[jira] Commented: (STR-3144) Bean Taglib Documentation Has Been
Unreadable FOR YEARS...
Posted by "Paul Benedict (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/STR-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43876#action_43876 ]
Paul Benedict commented on STR-3144:
------------------------------------
Niall, no problem :-) I am more than happy to be part of a team.
Original problem is part of an end-user (me) invalid assumption on how Maven works. What we needed was this: http://jira.codehaus.org/browse/MNG-1931
> 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.
[jira] Commented: (STR-3144) Bean Taglib Documentation Has Been
Unreadable FOR YEARS...
Posted by "Paul Benedict (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/STR-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43844#action_43844 ]
Paul Benedict commented on STR-3144:
------------------------------------
If you want to fix it, please bug the developer of the taglib plugin. I've tried unsuccessfully. I would like the markup unescaped as well. If nothing can be done, removing the tag reference will be our only option. Want to try helping? I would like the extra help!
http://maven-taglib.sourceforge.net/m2/
> 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.2.7, 1.2.8, 1.2.9, 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.
[jira] Commented: (STR-3144) Bean Taglib Documentation Has Been
Unreadable FOR YEARS...
Posted by "Niall Pemberton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/STR-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43875#action_43875 ]
Niall Pemberton commented on STR-3144:
--------------------------------------
P.S. Sorry Paul, I had the changes locally and had tested before I saw you had assigned this to yourself - so I just went ahead and committed
> 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.
[jira] Updated: (STR-3144) Bean Taglib Documentation Has Been
Unreadable FOR YEARS...
Posted by "Matthieu Chase Heimer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/STR-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthieu Chase Heimer updated STR-3144:
---------------------------------------
Attachment: struts1-taglib-pom.diff
Yes. I think it's only in the latest version of the taglib plugin (2.3.1) so maybe you tried it before 2.3.1. Here is what the page looks like with parseHtml set to true http://www.ej4l.org/site/tagreference.html. Notice there is sill a problem with the one sentence summaries of each lib but that's a bug in the taglib plugin. The page is rendered much better with this option turned on.
> 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
> 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.
[jira] Updated: (STR-3144) Bean Taglib Documentation Has Been
Unreadable FOR YEARS...
Posted by "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 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.