https://bz.apache.org/bugzilla/show_bug.cgi?id=57767
--- Comment #17 from Remy Maucherat ---
Yes, I would rather integrate it (if it works) then see about reuse. I also
don't think javadoc is a big issue either for this kind of code.
--
You are receiving this mail because:
You are the assignee
https://bz.apache.org/bugzilla/show_bug.cgi?id=57767
--- Comment #16 from Mark Thomas ---
If there is a possibility of reuse ( this is client side and the existing code
is server side) we'd need to be careful about which package / jar we put it in
to avoid adding unwanted dependencies for the Web
https://bz.apache.org/bugzilla/show_bug.cgi?id=57767
--- Comment #15 from Christopher Schultz ---
None of the Java classes in the authentication support patch have any Javadoc.
I'm -1 on accepting the patch on that basis alone. I've skimmed the code and it
otherwise looks good, but I have not tes
https://bz.apache.org/bugzilla/show_bug.cgi?id=61491
--- Comment #2 from Mark Thomas ---
I've managed to reproduce this.
It is triggered by a zero length message after a non-zero length message when
the compression context is retained between messages.
I'm starting to think about a fix.
--
Yo
Hi Mark,
Oracle is proposing a rapid release model for Java SE going-forward.
The high points are highlighted below, details of the changes can be
found on Mark Reinhold’s blog [1] , OpenJDK discussion email list [2].
Under the proposed release model, after JDK 9, we will adopt a strict,
tim
