Thanks for your responses and clarifications! Regarding the reasons for using the fork: We would love to move to the Apache Calcite instead of using the fork!
And we tried very hard to do it, especially during the rebase from 1.4 to 1.15 (DRILL-3993 <https://issues.apache.org/jira/browse/DRILL-3993>). But unfortunately, there left three Jiras, which weren't accepted by the Calcite community yet: CALCITE-2087 <https://issues.apache.org/jira/browse/CALCITE-2087>, CALCITE-2018 <https://issues.apache.org/jira/browse/CALCITE-2018> and CALCITE-1178 <https://issues.apache.org/jira/browse/CALCITE-1178>. Kind regards, Volodymyr Vysotskyi On Wed, Sep 12, 2018 at 7:39 PM Julian Hyde <[email protected]> wrote: > I can confirm what Josh says about OSSRH. You need to fill out a form with > Sonatype that convinces them that you own the groupId (basically a domain > name). Then they give you authorization to publish artifacts under that > groupId. For example, I publish artifacts under the sqlline and > net.hydromatic groupIds. > > > On Sep 12, 2018, at 9:28 AM, Josh Elser <[email protected]> wrote: > > > > Maven central is made up of a number of "Trusted" Maven repositories. > This includes the ASF and OSSRH Maven repositories. Many other > organizations run "mirrors" of central. > > > > The ASF Maven repo is published to by ASF projects who have gone through > the ASF release process. OSSRH allows any release which meets the criteria > described here[1]. As an individual, you are within your rights to publish > your fork of Calcite to OSSRH as long as there are no legal or trademark > concerns. It would be imperative to not cause confusion with official > Apache Calcite releases -- clear branding and separate Maven > groupId/artifactId "coordinates" should be sufficient. > > > > However, since you are (presumably) acting as a member of Apache Drill, > it would be very odd (and potentially against ASF policy) to make a release > of software that *isn't* using the ASF Maven resources. This gives me some > pause -- do you have an ASF member on your PMC you can run this by? > > > > Finally, as a Calcite PMC member, I feel obligated to ask why Drill > needs to maintain this fork, and see if there is something that can be done > from the Calcite side to get you "back on upstream"? Why the need to make > long-term plans to isolate Apache Drill from Apache Calcite? > > > > [1] https://central.sonatype.org/pages/ossrh-guide.html > > > > On 9/12/18 11:33 AM, Vova Vysotskyi wrote: > >> Hi all, > >> As you know, Drill uses its fork of Apache Calcite. > >> In DRILL-6711 <https://issues.apache.org/jira/browse/DRILL-6711> was > >> proposed to deploy Drill Calcite project artifacts > >> to Apache Maven repository or at least to the central maven repository. > >> I have looked for the similar cases of fork versions and didn't find > >> anything similar in the central repo. > >> Also, I have looked at the Sonatype OSSRH Jiras for similar cases > >> of deploying fork versions, but that projects used custom groupIds. > >> Could someone please give me the advice what is the acceptable way > >> of publishing the custom Drill Calcite artifacts to the central repo and > >> is it possible to publish them without changing groupId? > >> Kind regards, > >> Volodymyr Vysotskyi > >
