[
https://issues.apache.org/jira/browse/ARROW-13051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17374992#comment-17374992
]
Kouhei Sutou commented on ARROW-13051:
--------------------------------------
We don't need to use Artifactory for Java binaries.
I think that we can use staging feature (sorry, I'm not sure that this is
properly name) of Maven central:
https://cwiki.apache.org/confluence/display/ARROW/Release+Management+Guide#ReleaseManagementGuide-UpdatingJavaMavenartifactsinMavencentral
I think that 3., 4 and, 5. are replaced with:
3. the release manager signs the artifacts then uploads them as staged
artifacts to Maven central
4. the Java post release task publish the staged artifacts in Maven central
BTW, currently {{dev/release/verify-release-candidate.sh}} doesn't verify Java
artifacts. It just verify Java sources. We need to update
{{dev/release/verify-release-candidate.sh}} in the future...
> [Release][Packaging] Update the java post release task to use the crossbow
> artifacts
> ------------------------------------------------------------------------------------
>
> Key: ARROW-13051
> URL: https://issues.apache.org/jira/browse/ARROW-13051
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Developer Tools, Packaging
> Reporter: Krisztian Szucs
> Assignee: Anthony Louis Gotlib Ferreira
> Priority: Major
>
> We produce java jars using a crossbow tasks. Ideally we should download and
> deploy these packages instead of compiling them locally during the java post
> release task.
> See the produced jars at:
> https://github.com/ursacomputing/crossbow/releases/tag/actions-496-github-java-jars
> See more context at: https://github.com/apache/arrow/pull/10411
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
