[SPARK-49370][BUILD] maven.scaladoc.skip should not affect test code compilation#47858
Closed
pan3793 wants to merge 1 commit intoapache:masterfrom
Closed
[SPARK-49370][BUILD] maven.scaladoc.skip should not affect test code compilation#47858pan3793 wants to merge 1 commit intoapache:masterfrom
maven.scaladoc.skip should not affect test code compilation#47858pan3793 wants to merge 1 commit intoapache:masterfrom
Conversation
Member
Author
HyukjinKwon
approved these changes
Aug 26, 2024
Member
|
Merged to master. |
yaooqinn
approved these changes
Aug 26, 2024
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
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.
What changes were proposed in this pull request?
Move
maven.scaladoc.skipfrom thescala-maven-plugin's global configuration to itsattach-scaladocsexecution's configuration.Why are the changes needed?
maven.scaladoc.skipwas added in SPARK-43461 to speed up thedev/make-distribution.shby skipping scaladocs generation, but it was wrongly applied to a broader scope.Does this PR introduce any user-facing change?
It affects developers who use
build/mvn deploy -Dmaven.scaladoc.skip=trueto deploy the artifacts case, without this patch, wrong<module>-tests.jars (don't contain the test classes but only resources) will be produced.How was this patch tested?
before
after
Was this patch authored or co-authored using generative AI tooling?
No.