I just made a PR [1] that should address CALITE-5399 [2]. As discussed on Jira [2], the proposed solution should be sufficient. Making Proj4J as a compileOnly dependency should prevent the jar and the EPSG dataset from being included in any distribution of Calcite. When a user will call a spatial type function that rely on Proj4J (e.g. ST_Transform), Calcite will throw a ClassNotFoundException. The user will have to manually include Proj4J in its dependencies to use these functions.
Please notice that I’m more familiar with maven than gradle and would appreciate a double check on this. Thanks a lot for your help, Bertil [1] https://github.com/apache/calcite/pull/2988 [2] https://issues.apache.org/jira/browse/CALCITE-5399 > On 28 Nov 2022, at 20:28, Julian Hyde <jhyde.apa...@gmail.com> wrote: > > Yes, we must fix Proj4j (CALITE-5399) before 1.33. I believe Bertil is > working on it. > >> On Nov 28, 2022, at 4:06 AM, Ruben Q L <rube...@gmail.com> wrote: >> >> Thanks Jess for being RM of 1.33, and thanks Benchao for volunteering as RM. >> The updated list for future releases will be as follows: >> - 1.33.0 Jess Balint >> - 1.34.0 Duan Xiong >> - 1.35.0 Benchao Li >> >> There are currently 14 unresolved issues for 1.33: >> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333950 >> Many of them have a PR available, let's try to do a collective effort and >> review them ASAP (I remind everyone that you can assign a PR to yourself to >> let others know that you are taking care of it). >> As I mentioned on the initial email, let's try to finalize the remaining >> issues during these two weeks, to see if we can produce a RC0 by >> mid-December. >> >> Regarding the recent Proj4j license problem ( >> https://issues.apache.org/jira/browse/CALCITE-5399), should we consider >> this a blocking issue for 1.33? >> >> Best, >> Ruben >> >> >> On Fri, Nov 11, 2022 at 6:53 PM Jess Balint <jbal...@gmail.com> wrote: >> >>> Hi Ruben, >>> >>> Thanks for the note. I'm available for RM duty. Here's the list of issues >>> currently outstanding: >>> >>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CALCITE%20AND%20fixVersion%20%3D%201.33.0%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20%22In%20Review%22%2C%20%22In%20Implementation%22)%20ORDER%20BY%20priority%20DESC >>> >>> I'll pick up a couple of reviews and see if we can move out some of the >>> issues which haven't been started yet. >>> >>> Jess >>> >>> On Fri, Nov 11, 2022 at 3:20 AM Ruben Q L <rube...@gmail.com> wrote: >>> >>>> Hello, >>>> >>>> It's been two months since our last release [1], if we want to keep our >>>> rhythm, I'd suggest to produce the next one before the end of the year. >>>> >>>> As usual, according to our Jira dashboard [2] and Github [3], there are >>>> many pending issues that could / should be part of the release. I'd >>> propose >>>> to make a collective effort to try to clean up our 1.33 backlog and merge >>>> the PRs which are in a good state. Shall we give ourselves around four >>>> weeks and aim at approximately December 11th for the first RC? >>>> >>>> According to this thread [4], the list of the last Release Managers is as >>>> follows: >>>> - 1.30.0 Liya Fan >>>> - 1.31.0 Andrei Sereda >>>> - 1.32.0 Julian Hyde (originally Jess Balint, switched with 1.33) >>>> --- >>>> - 1.33.0 Jess Balint (originally Julian Hyde, switched with 1.32) >>>> - 1.34.0 Duan Xiong >>>> >>>> @Jess, are you still available to be the next RM for 1.33.0? >>>> >>>> Do we have any other volunteers to be RM for the next releases? >>>> >>>> Best regards, >>>> Ruben >>>> >>>> [1] https://calcite.apache.org/news/2022/09/10/release-1.32.0/ >>>> [2] >>>> >>> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333950 >>>> [3] https://github.com/apache/calcite/pulls >>>> [4] https://lists.apache.org/thread/ykbhhxmljw6wg50rxs6ypp35173hlkdv >>>> >>> >
signature.asc
Description: Message signed with OpenPGP
