[
https://issues.apache.org/jira/browse/S2GRAPH-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15646227#comment-15646227
]
Jong Wook Kim commented on S2GRAPH-115:
---------------------------------------
It looks like that using the Apache Parent POM is not necessary as the parent
pom provides [some convenience settings|https://maven.apache.org/pom/asf/] for
Maven which needs to be reimplemented if we're using SBT.
Otherwise the parent POM will unnecessarily add HTTP calls for resolving it
(remember seeing something like {{resolving org.apache#apache;18}} ALL the
time?).
I also noted that at least one Existing Scala project in ASF [does not
use|https://repo1.maven.org/maven2/org/apache/gearpump/gearpump-core_2.11/0.8.1/gearpump-core_2.11-0.8.1.pom]
the Apache parent POM. So this should not be a blocker for our release.
I'm mostly done making the artifacts produced by {{sbt publishSigned}} to
satisfy the other requirements, and will create a pull request momentarily.
> 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)
