Skip to content

8359760: Remove the jdk.jsobject module #26393

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

Closed

Conversation

kevinrushforth
Copy link
Member

@kevinrushforth kevinrushforth commented Jul 18, 2025

This PR removes the terminally-deprecated jdk.jsobject module from the JDK. This module is now shipped with JavaFX, and has been since JavaFX 24.

The following files still reference jdk.jsobject (or the netscape.javascript package). They are not modified because these files reflect the state of earlier releases, which do have the jdk.jsobject module.

src/jdk.compiler/share/data/symbols/jdk.jsobject-9.sym.txt
src/jdk.compiler/share/data/symbols/jdk.jsobject-A.sym.txt
src/jdk.compiler/share/data/symbols/jdk.jsobject-B.sym.txt
src/jdk.compiler/share/data/symbols/jdk.jsobject-C.sym.txt
src/jdk.compiler/share/data/symbols/jdk.jsobject-E.sym.txt
src/jdk.compiler/share/data/symbols/jdk.jsobject-G.sym.txt
src/jdk.compiler/share/data/symbols/jdk.jsobject-M.sym.txt
src/jdk.compiler/share/data/symbols/jdk.jsobject-O.sym.txt
src/jdk.compiler/share/data/symbols/jdk.scripting.nashorn-8.sym.txt
src/jdk.compiler/share/data/symbols/jdk.scripting.nashorn-9.sym.txt
src/jdk.compiler/share/data/symbols/jdk.scripting.nashorn-B.sym.txt
src/jdk.compiler/share/data/symbols/jdk.scripting.nashorn-F.sym.txt
src/jdk.compiler/share/data/symbols/symbols
src/jdk.javadoc/share/classes/jdk/javadoc/internal/doclets/toolkit/resources/releases/element-list-10.txt
src/jdk.javadoc/share/classes/jdk/javadoc/internal/doclets/toolkit/resources/releases/element-list-9.txt

I have run tier1, tier2, and tier3 tests, as well as local tests with JavaFX WebView.


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue
  • Change requires CSR request JDK-8362628 to be approved

Issues

  • JDK-8359760: Remove the jdk.jsobject module (Enhancement - P4)
  • JDK-8362628: Remove the jdk.jsobject module (CSR)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/26393/head:pull/26393
$ git checkout pull/26393

Update a local copy of the PR:
$ git checkout pull/26393
$ git pull https://git.openjdk.org/jdk.git pull/26393/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 26393

View PR using the GUI difftool:
$ git pr show -t 26393

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26393.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Jul 18, 2025

👋 Welcome back kcr! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Jul 18, 2025

@kevinrushforth This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8359760: Remove the jdk.jsobject module

Reviewed-by: rriggs, iris, alanb

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 18 new commits pushed to the master branch:

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@RogerRiggs, @irisclark, @AlanBateman) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

@openjdk
Copy link

openjdk bot commented Jul 18, 2025

@kevinrushforth The following labels will be automatically applied to this pull request:

  • build
  • core-libs
  • javadoc

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command.

@kevinrushforth
Copy link
Member Author

/skara label client

@openjdk
Copy link

openjdk bot commented Jul 18, 2025

@kevinrushforth
The client label was successfully added.

@openjdk openjdk bot added the csr Pull request needs approved CSR before integration label Jul 18, 2025
@kevinrushforth
Copy link
Member Author

@RogerRiggs @AlanBateman Can you review this PR to remove the jdk.jsobject module, which was deprecated for removal by PR #20555 ?

@kevinrushforth kevinrushforth marked this pull request as ready for review July 22, 2025 14:57
@openjdk openjdk bot added the rfr Pull request is ready for review label Jul 22, 2025
@mlbridge
Copy link

mlbridge bot commented Jul 22, 2025

Webrevs

@AlanBateman
Copy link
Contributor

I did a quick scan and the updates to the conf, the removal, and the test changes look okay. Happy to review the CSR when you have it ready.

@@ -302,8 +302,6 @@ jdk.jshell
jdk.jshell.execution
jdk.jshell.spi
jdk.jshell.tool
module:jdk.jsobject
Copy link
Contributor

Choose a reason for hiding this comment

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

There is a similar pair in test/langtools/jdk/javadoc/doclet/testRecordTypes/jdk17/element-list.
Can it be removed? Unless it causes a test failure.

Copy link
Member Author

Choose a reason for hiding this comment

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

I wondered about that, and originally was going to remove it, but then noticed that the test in question parses the JDK 17 API docs (which does have the jdk.jsobject module).

https://github.com/openjdk/jdk/blob/e70c702d6f864b494dc7df3eea4f1a317a3bc981/test/langtools/jdk/javadoc/doclet/testRecordTypes/TestRecordTypes.java#L55-56

    private static final String externalDocs =
        "https://docs.oracle.com/en/java/javase/17/docs/api";

I suspect that the test will run just fine if I remove it. I don't mind either way. What would you recommend?

Copy link
Contributor

Choose a reason for hiding this comment

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

I ran the test and then removed those lines and the test still passed.
I'd remove them to avoiding leaving a (little) mess behind.

Copy link
Member Author

Choose a reason for hiding this comment

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

As expected, the above test passes fine if I remove the jsobject entries from test/langtools/jdk/javadoc/doclet/testRecordTypes/jdk17/element-list. I'll go ahead and remove them, since it seems like good cleanup.

Copy link
Contributor

Choose a reason for hiding this comment

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

@hns Would it be possible to confirm that it's okay to remove this from the doclet tests?

Copy link
Member

@hns hns Jul 23, 2025

Choose a reason for hiding this comment

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

The list is used as list of external linkable modules/packages for the -linkoffline option. Since the list is for JDK 17 the entry could be left in the list, but as the test doesn't try to link to the module removing it doesn't make any difference.

Copy link
Member

Choose a reason for hiding this comment

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

Maybe my previous comment was a bit unclear. Both options are okay, leaving the entries and removing them.

Copy link
Member Author

Choose a reason for hiding this comment

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

Thanks. In that case, I'll stick with the current state of the PR which removes them.

@kevinrushforth
Copy link
Member Author

I did a quick scan and the updates to the conf, the removal, and the test changes look okay. Happy to review the CSR when you have it ready.

Thanks. The CSR is now ready to review: https://bugs.openjdk.org/browse/JDK-8362628

Copy link
Contributor

@RogerRiggs RogerRiggs left a comment

Choose a reason for hiding this comment

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

look good.

@openjdk openjdk bot added ready Pull request is ready to be integrated and removed csr Pull request needs approved CSR before integration labels Jul 22, 2025
@kevinrushforth
Copy link
Member Author

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label Jul 23, 2025
@openjdk
Copy link

openjdk bot commented Jul 23, 2025

@kevinrushforth
Your change (at version 2858cd3) is now ready to be sponsored by a Committer.

@irisclark
Copy link
Member

/sponsor

@openjdk
Copy link

openjdk bot commented Jul 23, 2025

Going to push as commit 594c080.
Since your change was applied there have been 18 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Jul 23, 2025
@openjdk openjdk bot closed this Jul 23, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review sponsor Pull request is ready to be sponsored labels Jul 23, 2025
@openjdk
Copy link

openjdk bot commented Jul 23, 2025

@irisclark @kevinrushforth Pushed as commit 594c080.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

@kevinrushforth kevinrushforth deleted the 8359760-rm-jsobject branch July 23, 2025 15:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

5 participants