-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
ARROW-16943: [Java][Packaging] Fix nigthly build problem that generates excessive jars #13485
ARROW-16943: [Java][Packaging] Fix nigthly build problem that generates excessive jars #13485
Conversation
|
@github-actions crossbow submit java-jars |
Revision: 9644eb5 Submitted crossbow builds: ursacomputing/crossbow @ actions-442b8b8306
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
I merge this as a workaround but I think that the root cause of this is using a self-hosted runner not a GitHub-hosted runner.
See also my comment on JIRA: https://issues.apache.org/jira/browse/ARROW-16943?focusedCommentId=17561175&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17561175
Thanks @kou |
…es excessive jars (apache#13485) Since June 24 the nightly build is generating multiple jars for the same module. In that example: https://github.com/ursacomputing/crossbow/releases/tag/nightly-packaging-2022-06-24-0-github-java-jars you can find three different jars for the arrow-gandiva. The commit purpose is clean the .m2 folder before executing the clean install command and copy the artifacts to the folder where they will be uploaded. Authored-by: Anthony Louis <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
Since June 24 the nightly build is generating multiple jars for the same module.
In that example: https://github.com/ursacomputing/crossbow/releases/tag/nightly-packaging-2022-06-24-0-github-java-jars you can find three different jars for the arrow-gandiva.
The commit purpose is clean the .m2 folder before executing the clean install command and copy the artifacts to the folder where they will be uploaded.