[
https://issues.apache.org/jira/browse/SPARK-22522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253918#comment-16253918
]
Felix Cheung commented on SPARK-22522:
--------------------------------------
sorry about the confusion - to clarify, the repo is the same in the existing
process we have, this JIRA is only proposing a tooling change, not a
destination change. In fact, during the officially documented ASF release
process, once a release is voted it can be promoted which gets the maven
artifacts to central automatically (again, same as today)
http://www.apache.org/dev/publishing-maven-artifacts.html#promote
Congratulations, your vote was successful. The last step is to promote the
artifacts to the release repository where they will get picked up by Central.
> Convert to apache-release to publish Maven artifacts to
> Nexus/repository.apache.org
> -----------------------------------------------------------------------------------
>
> Key: SPARK-22522
> URL: https://issues.apache.org/jira/browse/SPARK-22522
> Project: Spark
> Issue Type: Improvement
> Components: Build
> Affects Versions: 2.3.0
> Reporter: Felix Cheung
> Priority: Minor
>
> see http://www.apache.org/dev/publishing-maven-artifacts.html
> ...at the very least we need to revisit all the calls to curl (and/or gpg) in
> the release-build.sh for the publish-release path - seems like some errors
> are ignored (running into that myself) and it would be very easy to miss
> publishing one or more or all files.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
