[
https://issues.apache.org/jira/browse/ARROW-15486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484036#comment-17484036
]
Chao Sun commented on ARROW-15486:
----------------------------------
[~kou] after you the RC on nexus is closed, the artifacts will be available in
the staging repository, and users can update their Maven pom.xml using the
following settings:
{code}
<repository>
<id>staged</id>
<name>staged-releases</name>
<url>https://repository.apache.org/content/repositories/staging/</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
{code}
(and of course, they need to update the Arrow version to the one specified in
the RC).
> [Relase][Java] Verify staged maven artifacts
> --------------------------------------------
>
> Key: ARROW-15486
> URL: https://issues.apache.org/jira/browse/ARROW-15486
> Project: Apache Arrow
> Issue Type: Improvement
> Reporter: Krisztian Szucs
> Priority: Major
>
> We have two tests right now:
> 1. Execute {{mvn test}} from the source tarball's java directory testing the
> source
> https://github.com/apache/arrow/blob/master/dev/release/verify-release-candidate.sh#L278
> 2. Verify the checksums and signatures of the uploaded maven artifacts
> https://github.com/apache/arrow/blob/master/dev/release/verify-release-candidate.sh#L766
> But we don't actually *test* the packages. We should add that to the
> verification scripts, since 7.0 is going to be the first release shipping the
> jars with bundled JNI libraries.
> cc [~kou] [~anthonylouis]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
