[
https://issues.apache.org/jira/browse/SEDONA-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17690586#comment-17690586
]
Gregoire Leleu commented on SEDONA-248:
---------------------------------------
Yes, this is fine for local dev, but it's hard for regular R users who just
want to have the latest features (which is the point of CI/CD). I can try to
make the documentation clear, but it remains i) hard to get to the latest
artifact for inexperienced users and ii) prone to errors (forgetting to update
env variables etc.).
Having an accessible nightly build would be great, but yes, not a priority. The
python package doesn't have the same issue?
> 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)
