[SPARK-56675][BUILD] Make sbt publishLocal work#55624
Open
sarutak wants to merge 1 commit intoapache:masterfrom
Open
[SPARK-56675][BUILD] Make sbt publishLocal work#55624sarutak wants to merge 1 commit intoapache:masterfrom
sarutak wants to merge 1 commit intoapache:masterfrom
Conversation
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?
This PR fixes an issue that
sbt publishLocaldoesn't work.The reason is that
packageDoc/publishArtifactdoesn't work (sosbt docalso doesn't work).In the Spark community, API documents are generated using
unidocand I feel having API documents in~/.m2or~/.ivy2is not so useful.So, the solution is publishing API documents by
packageDoc / publishArtifact := false.In addition, this PR allows developers to configure whether to publish source JARs by an environment variable
PUBLISH_PACKAGE_SRC. The default value isfalse, which is the same behavior asmvn install.Why are the changes needed?
Having artifacts in
~/.m2or~.ivy2is useful for downstream developersDoes this PR introduce any user-facing change?
No.
How was this patch tested?
Confirmed artifacts are in both
~/.m2and~/.ivy2by the following command.Also confirmed
*-sources.jarare in both~/.m2and~/.ivy2by the following command.Was this patch authored or co-authored using generative AI tooling?
No.