> Most of the JDK code base has been transitioned to UTF-8, but not all. This
> has recently become an acute problem, since our mixing of iso-8859-1 and
> utf-8 in properties files confused the version of `sed` that is shipped with
> the new macOS 15.4.
>
> The fix is basically simple, and incl
On Thu, 10 Apr 2025 14:28:02 GMT, Magnus Ihse Bursie wrote:
> Most of the JDK code base has been transitioned to UTF-8, but not all. This
> has recently become an acute problem, since our mixing of iso-8859-1 and
> utf-8 in properties files confused the version of `sed` that is shipped with
>
This is a WIP to move the JDK source code base to fully UTF-8, and to ensure
tools knows about this.
-
Commit messages:
- Fix flags for Windows
- Mark java and native source code as utf-8
- Don't convert properties files to iso-8859-1.
- Tell tools we use utf-8
- Replace iso-885
On Fri, 11 Apr 2025 21:26:08 GMT, Roger Riggs wrote:
> The JavaIOFilePermissionAccess interface is removed from SharedSecrets and
> its implementation (FilePermCompat.java) used by the test is moved to java.io
> FilePermission where cross package access is not needed.
> The test FilePermission
On Sun, 13 Apr 2025 09:49:46 GMT, Chen Liang wrote:
> Proxy currently places proxy classes that proxy interfaces with
> package-private return types in dynamic modules. This means that if a return
> value is non-null, Proxy cannot return it and throws IllegalAccessError.
>
> This patch changes
On Fri, 11 Apr 2025 21:26:08 GMT, Roger Riggs wrote:
> The JavaIOFilePermissionAccess interface is removed from SharedSecrets and
> its implementation (FilePermCompat.java) used by the test is moved to java.io
> FilePermission where cross package access is not needed.
> The test FilePermission
On Sun, 13 Apr 2025 09:49:46 GMT, Chen Liang wrote:
> Proxy currently places proxy classes that proxy interfaces with
> package-private return types in dynamic modules. This means that if a return
> value is non-null, Proxy cannot return it and throws IllegalAccessError.
>
> This patch changes
Proxy currently places proxy classes that proxy interfaces with package-private
return types in dynamic modules. This means that if a return value is non-null,
Proxy cannot return it and throws IllegalAccessError.
This patch changes strategy so proxy classes for any reference to
package-private
On Sun, 13 Apr 2025 09:49:46 GMT, Chen Liang wrote:
> Proxy currently places proxy classes that proxy interfaces with
> package-private return types in dynamic modules. This means that if a return
> value is non-null, Proxy cannot return it and throws IllegalAccessError.
>
> This patch changes
On Fri, 4 Apr 2025 13:36:19 GMT, Hannes Wallnöfer wrote:
> Please review an enhancement to treat classes and interfaces that are not
> included and not unconditionally exported as hidden. This means they do not
> show up in the generated documentation even if they are implemented or
> extended
On Fri, 11 Apr 2025 21:26:08 GMT, Roger Riggs wrote:
> The JavaIOFilePermissionAccess interface is removed from SharedSecrets and
> its implementation (FilePermCompat.java) used by the test is moved to java.io
> FilePermission where cross package access is not needed.
> The test FilePermission
On Tue, 11 Feb 2025 17:56:04 GMT, Chen Liang wrote:
> The return value adaption of Proxy is problematic, that it may attempt to
> access package-private types inaccessible to its package in a `checkcast`
> instruction, which causes `IllegalAccessError` if the returned object is not
> `null`. T
12 matches
Mail list logo
