[
https://issues.apache.org/jira/browse/SEDONA-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694705#comment-17694705
]
Gregoire Leleu commented on SEDONA-248:
---------------------------------------
I'm more concerned with users being able to find the jars than passing them to
Spark (the ENV is fine for R users). I guess Python users have the same issue:
looking for the artefacts in GitHub action workflows is quite advanced.
Would it be possible to create a "SNAPSHOT" release that would go here
[https://github.com/apache/sedona/releases] and be updated everytime the
workflows run? I've seen other projects do it. That way we can tell users to
get it from this location which stays the same.
Also, the generated jars don't include the common jar, should it? When I
manually specify the jars I need to add it.
> R – Let dev version of R package use SNAPSHOT jars
> --------------------------------------------------
>
> Key: SEDONA-248
> URL: https://issues.apache.org/jira/browse/SEDONA-248
> Project: Apache Sedona
> Issue Type: Improvement
> Reporter: Gregoire Leleu
> Priority: Major
> Attachments: image-2023-02-17-11-45-38-710.png
>
>
> Currently, one source of error is that the dev version of the R package calls
> the Sedona jars from the previous release. Right now the dev version (1.4.0)
> by default calls the 1.3.1 jars.
> You can override it, but you either need to build the jars yourself (most R
> users won't do it) or get them somewhere (but where?).
> Would it be possible to:
> * Make the jars available in a maven repo (I would have assumed
> [https://repository.apache.org/content/groups/snapshots/org/apache/sedona/sedona-core-3.0_2.13/]
> from the documentation, but 1.4.0 isn't there)
> * Have the dev version point to those jars
> * Change to the regular repo for the release
> In terms of cache: will the jar cache system update the Sedona SNAPSHOT jars
> if the name doesn't change?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
