Skip to content

Updated 0.46.0 Release note with new features #19970

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 8, 2024

Conversation

Sreekala-Gopakumar
Copy link
Contributor

Updated the release note with the remaining issues in 0.46.0 release

[skip ci]
Signed-off-by: Sreekala Gopakumar [email protected]

@Sreekala-Gopakumar
Copy link
Contributor Author

@TobiAjila, @pshipton - I have updated the release notes with all the remaining issues that were documented for the 0.46.0 release. Please check and merge. Thanks!

<td valign="top"><a href="https://github.com/eclipse-openj9/openj9/pull/19323">#19323</a>, <a href="https://github.com/eclipse-openj9/openj9/pull/19442">#19442</a></td>
<td valign="top">The <tt>-XX:[+|-]ShareOrphans</tt> option is added to control storing of orphan classes in the shared classes cache.</td>
<td valign="top">All versions</td>
<td valign="top">When <tt>-Xshareclasses</tt> was specified, only those class loaders that implemented the OpenJ9's public shared classes cache APIs (and its child class loaders) could store classes to the shared classes cache. Custom class loaders that did not implement these cache APIs cannot pass the module or class path information to the VM. Classes of such class loaders were not stored to the cache.
Copy link
Contributor

@tajila tajila Aug 8, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor tense changes:

was specified, only the class loaders that implemented the OpenJ9's public shared classes cache APIs (and its child class loaders) could store classes to the shared classes cache. Custom class loaders that did not implement these cache APIs couldn't pass the module or class path information to the VM. Classes of such class loaders were not stored to the cache.

Now, users can enable class sharing from all class loaders, irrespective of whether the class loader implements the shared classes cache API, with the -XX:+ShareOrphans option.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We avoid using the term "users". I will change the sentence to "Now, you can enable..."

Updated the release note with the remaining issues in 0.46.0 release. A link correction made.

[skip ci]
Signed-off-by: Sreekala Gopakumar [email protected]
@Sreekala-Gopakumar
Copy link
Contributor Author

@tajila - I have incorporated the changes. Please check. Thanks!

@tajila tajila merged commit dc0af4f into eclipse-openj9:master Aug 8, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants