DO NOT REPLY [Bug 19301] - junitreport fails for long string literals
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19301. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19301 junitreport fails for long string literals --- Additional Comments From [EMAIL PROTECTED] 2004-02-06 00:25 --- OK will put this into ant 1.6.1 Antoine - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 19301] - junitreport fails for long string literals
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19301. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19301 junitreport fails for long string literals --- Additional Comments From [EMAIL PROTECTED] 2004-01-24 13:36 --- There is no XSLT-only fix to this as far as I can see. The main problem is that a function such as translate() only operates with single character rather than string so you are left with a recursive template. An easy fix (and that should probably speed up things as well) is to use Xalan Java extension. I don't have time right now to fully test the solution but here is it: edit xsl:stylesheet root element and add the attribute xmlns:stringutils=xalan://org.apache.tools.ant.util.StringUtils Replace the JS-escape template with the following one: xsl:template name=JS-escape xsl:param name=string/ xsl:param name=tmp1 select=stringutils:replace(string ($string),'\','\\')/ xsl:param name=tmp2 select=stringutils:replace(string ($tmp1),quot;'quot;,quot;\apos;quot;)/ xsl:value-of select=$tmp2/ /xsl:template Please give your feedback. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 19301] - junitreport fails for long string literals
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19301. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19301 junitreport fails for long string literals [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2004-01-22 10:53 --- *** Bug 26329 has been marked as a duplicate of this bug. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 19301] - junitreport fails for long string literals
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19301. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19301 junitreport fails for long string literals [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2004-01-22 10:55 --- *** Bug 26230 has been marked as a duplicate of this bug. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 19301] - junitreport fails for long string literals
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19301. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19301 junitreport fails for long string literals [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] ||.net --- Additional Comments From [EMAIL PROTECTED] 2003-11-26 12:50 --- *** Bug 24799 has been marked as a duplicate of this bug. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 19301] - junitreport fails for long string literals
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19301. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19301 junitreport fails for long string literals --- Additional Comments From [EMAIL PROTECTED] 2003-10-18 13:47 --- Specifying a styledir that contains modified stylesheets is indeed a possible workaround. I agree that putting arbitrary limits into the default style sheets doesn't seem like a good idea. On the other hand it is the default setup that is broken, not some exotic configuration. Perhaps a more convenient solution for people who run into this problem would be to have a switch junit/[EMAIL PROTECTED]yes that supresses output of the test property data. Such a switch may even be welcomed by others as well, as I suspect this would reduce the size of the generated test output files and significantly speed up transformation time. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 19301] - junitreport fails for long string literals
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19301. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19301 junitreport fails for long string literals [EMAIL PROTECTED] changed: What|Removed |Added Summary|junitreport fails |junitreport fails for long ||string literals - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 19301] - junitreport fails for long string literals
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19301. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19301 junitreport fails for long string literals [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2003-10-14 14:20 --- *** Bug 20977 has been marked as a duplicate of this bug. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 19301] - junitreport fails for long string literals
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19301. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19301 junitreport fails for long string literals --- Additional Comments From [EMAIL PROTECTED] 2003-10-14 14:25 --- You could use a copy of Ant's stylesheets, add the snippet above to it and use junitreport's styledir attribute. I wouldn't want to hardcode any arbitrary limit into the default stylesheets, even if too long literals would cause problems with all existing xslt processors. Maybe Saxon works, maybe a future version of Xalan will work. If we fix the stylesheets now, users may complain about truncated output in the future. Could you please try my advice above and verify that it works for you? If so I'd put a pointer into the FAQ (and junitreport's manual) and close this report. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 19301] - junitreport fails
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19301. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19301 junitreport fails --- Additional Comments From [EMAIL PROTECTED] 2003-04-25 00:52 --- Created an attachment (id=6002) The test result file that causes junitreport to fail.
DO NOT REPLY [Bug 19301] - junitreport fails
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19301. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19301 junitreport fails --- Additional Comments From [EMAIL PROTECTED] 2003-04-25 12:51 --- I tracked down the problem to the JS-escape template, which produces a StackOverFlowError with Xalan 2.5D1 if the string parameter passed to the template is too long, as can easily happen when processing the java.class.path property. Not sure where the real limit is, all I know is that 7952 characters is too much :-) A temporary fix is to simply skip any long values and display them as '...' instead: xsl:when test=string-length($string) 1000 xsl:text.../xsl:text /xsl:when
