[jvm-packages] Fix JVM docs build, by making LabeledPoint a Java class#11545
Merged
Conversation
hcho3
changed the title
LabeledPoint a Java classLabeledPoint a Java class
Collaborator
Author
|
@wbo4958 @WeichenXu123 Can I get a review on this? |
trivialfis
approved these changes
Jul 3, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Unblock the CI by fixing the failing JVM docs build.
For some reason, the JavaDoc plugin is no longer able to resolve references to
LabeledPoint, which is currently a Scala class.To get the docs fixed, re-implement
LabeledPointas a Java class instead. This results into lots of boilerplate. When we transition to JVM 17+ (per #11510), we will be able to use a record class instead.