The changes to classes in the security component look fine. One question
I have is about the change to javax/xml/crypto/dsig/Manifest.java. Was
there a specific error here or did you just want to make this cleaner by
removing all of the html special character handling? The reason I ask is
that
On 11/06/2013 13:08, Sean Mullan wrote:
The changes to classes in the security component look fine. One
question I have is about the change to
javax/xml/crypto/dsig/Manifest.java. Was there a specific error here
or did you just want to make this cleaner by removing all of the html
special
I eyeballed the patch file. Looks fine to me.
It is really nice to have a tool to that operates on the actual source.
-Chris.
On 10/06/2013 11:31, Alan Bateman wrote:
About 8 months ago I tried an early build of doclint [1] and used it to
fix up a bunch issues at the time [2]. It's been
This looks good. Thank you for taking this on Alan.
Best
Lance
On Jun 10, 2013, at 6:31 AM, Alan Bateman wrote:
About 8 months ago I tried an early build of doclint [1] and used it to fix
up a bunch issues at the time [2]. It's been awhile, so I decided to try out
the latest version to
?
Thanks,
iris
-Original Message-
From: Alan Bateman
Sent: Monday, June 10, 2013 3:32 AM
To: core-libs-dev
Subject: 8016217: More javadoc warnings
About 8 months ago I tried an early build of doclint [1] and used it to fix up
a bunch issues at the time [2]. It's been awhile, so I decided
On 10/06/2013 18:29, Iris Clark wrote:
Hi, Alan.
The changes look good to me.
One thing caught my eye. In java.util.Calendar, around lines 2681 and later around 2702 you
removed the blockquote
--- old/src/share/classes/java/util/Calendar.java 2013-06-10
10:37:52.585879060 +0100
+++
I took a pass through the patch and nothing leaped out at me either. I wondered
about the use of nbsp; to prevent an expression from breaking across lines but
decided it's OK.
On Jun 10 2013, at 03:31 , Alan Bateman wrote:
About 8 months ago I tried an early build of doclint [1] and used it
