[
https://issues.apache.org/jira/browse/S2GRAPH-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15618794#comment-15618794
]
Jong Wook Kim commented on S2GRAPH-115:
---------------------------------------
[As I mentioned in the mailing
list|http://markmail.org/message/ekbki6ykgzsydh5b] we need quite a few things
to make the Maven Central release.
Apart from the access info, we need to know what we have to do on the POM and
the JARs; we might need a lot of pomPostProcess in the SBT settings.
- Do we need to have Apache as the parent POM of org.apache.s2graph:s2graph,
and make it the parent POM of the S2Graph subjects?
- What subprojects should go to Maven Central?
> 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)
