[ https://issues.apache.org/jira/browse/S2GRAPH-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15534677#comment-15534677 ]
Jong Wook Kim commented on S2GRAPH-115: --------------------------------------- As we've discussed in the dev mailing list, we can stop using our custom fork of asynchbase, by some bytecode weaving. I'll follow up in a separate issue. Speaking of Maven release and wider user adoption, does/should s2graph cross-compile in 2.10? > 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)