[
https://issues.apache.org/jira/browse/S2GRAPH-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15646485#comment-15646485
]
DOYUNG YOON commented on S2GRAPH-115:
-------------------------------------
[~jongwook] Thanks for the contribution!
Regarding sub projects, We were having discussion on merging followings into
one subproject.
# spark: helper methods for spark streaming.
# loader: bulk loader batch job.
# s2counter_loader: Spark streaming jobs for counter.
[thread|https://lists.apache.org/thread.html/cdcc3ff3e590861a5c149a6d3032a2e0da8b265deb9783ce5a2baf38@%3Cdev.s2graph.apache.org%3E]
We should discuss above topic and decide how to maintain sub projects, then I
think we can decide what will be published specifically.
In my opinion, all subjects need to be configured to be published for at least
0.1.1 release.
> 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)
