[
https://issues.apache.org/jira/browse/S2GRAPH-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15646343#comment-15646343
]
Jong Wook Kim commented on S2GRAPH-115:
---------------------------------------
We'll also need to find out if the ASF repository is happy with our signed
artifacts, and I propose that we do the following:
- decide which subprojects specifically to publish as Maven artifacts.
- override the version to {{0.1.0}} temporarily, and run publishSigned, to
publish the artifacts to ASF staging repository.
- test if the ASF repository accepts it.
I think this should be fine, since we didn't edit anything in the source tree
except the SBT settings. Let me know what you guys think.
> Release binary artifacts to Maven Central
> -----------------------------------------
>
> Key: S2GRAPH-115
> URL: https://issues.apache.org/jira/browse/S2GRAPH-115
> Project: S2Graph
> Issue Type: Improvement
> Affects Versions: 0.1.0
> Reporter: Sergio Fernández
> Priority: Minor
>
> Current 0.1.0 release candidate (RC4) does not provide binary artifacts.
> Although not strictly required, that's a common practice that helps on the
> project usage adoption. Therefore it would be nice that upcoming releases
> would do it.
> At http://www.apache.org/dev/publishing-maven-artifacts.html you can find the
> documentation on how to publishing Maven artifacts using the ASF
> infrastructure.
> Such process would require to figure out how to get rid of a custom
> dependency not available in Maven Central
> ({{org.hbase:asynchbase:1.7.2-S2GRAPH}}).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
