DO NOT REPLY [Bug 46933] Using Java 1.5 in StringManager

2009-04-28 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=46933 Jens Kapitza changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|

DO NOT REPLY [Bug 46933] Using Java 1.5 in StringManager

2009-04-28 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=46933 --- Comment #6 from Mark Thomas 2009-04-28 06:14:54 PST --- This has been fixed in 6.0.x and will be in 6.0.20 onwards. This issue can be marked as fixed once the second patch is moved to a new bugzilla entry. -- Configure bugmail: h

DO NOT REPLY [Bug 46933] Using Java 1.5 in StringManager

2009-04-28 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=46933 --- Comment #5 from Mark Thomas 2009-04-28 05:00:41 PST --- Can you create a new bugzilla issue for your second patch please. We try and keep each bugzilla entry to s single problem. Cheers. -- Configure bugmail: https://issues.apach

DO NOT REPLY [Bug 46933] Using Java 1.5 in StringManager

2009-04-27 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=46933 --- Comment #4 from Jens Kapitza 2009-04-27 06:21:29 PST --- Created an attachment (id=23550) --> (https://issues.apache.org/bugzilla/attachment.cgi?id=23550) do caching the resources like the docu say it do caching the resources l

DO NOT REPLY [Bug 46933] Using Java 1.5 in StringManager

2009-04-09 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=46933 Mark Thomas changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED

DO NOT REPLY [Bug 46933] Using Java 1.5 in StringManager

2009-04-08 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=46933 Jens Kapitza changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

DO NOT REPLY [Bug 46933] Using Java 1.5 in StringManager

2009-04-08 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=46933 --- Comment #1 from Mark Thomas 2009-04-08 04:09:31 PST --- Thanks for the patch. It can actually be even simpler as there is no longer a need to ensure that the args provided are non-null. This was only an issue with very early JVMs.