[
https://issues.apache.org/jira/browse/SEDONA-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694922#comment-17694922
]
Jia Yu commented on SEDONA-248:
-------------------------------
[~gregleleu]
1. I think this is a good idea. I will try to set up a github action to auto
upload jars to github releases.
2. It actually "includes" the common jar. But many things changed in Sedona
1.4.0. Everything by default is not packaged but put in 'compile' scope. This
means
(1) If a user uses an environment that can resolve and download transparent
Maven dependencies (e.g., --package org.apache.sedona:python-adapter:1.4.0),
python-adapter should work as usual. The environment will download Maven jars.
(2) If a user manually copies jars to a location, he/she needs to use
sedona-spark-shaded-1.4.0.jar instead of python-adapter. This shaded jar
includes all dependencies.
This behavior change is to resolve the long overdue issue in Sedona dependency
management. The old shade-everything packaging strategy often pollutes the
downstream project environment.
> 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)
