[
https://issues.apache.org/jira/browse/SEDONA-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17696371#comment-17696371
]
Jia Yu commented on SEDONA-248:
-------------------------------
[~gregleleu] For spark-shaded, I believe you can just grab the jar that has the
following name sedona-spark-shaded-3.0_[].jar [] could be either 2.12 or 2.13.
There are many other jars in spark-shaded/target folder so you might want to
use regex to match the pattern.
I don't think in the long term, it is feasible to copy others jars (such as
core + sql + viz + geotools-wrapper) instead of spark-shaded. Because if you
look at the main pom.xml of Sedona, we have many more dependencies and we
expect to add more in the future. It is hard to enumerate all jars in Sedona R.
So I think we'd better just use sedona-spark-shaded.
> 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)
