[ 
https://issues.apache.org/jira/browse/SEDONA-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17695920#comment-17695920
 ] 

Gregoire Leleu commented on SEDONA-248:
---------------------------------------

Ok,

Manually: shaded + viz. Can you make shaded part of the generated jars? (here I 
believe 
[https://github.com/apache/sedona/blob/master/.github/workflows/java.yml#L68)|https://github.com/apache/sedona/blob/master/.github/workflows/java.yml#L68]

Not manually: we keep core + sql + viz, they will be called from Maven (+ 
dependency resolution etc.)?

3rd pary: understood for cdm-core + geotools-wrapper. Is geotools wrapper 
1.4.0-28.2 on Maven?
BTW: the geotools wrapper version is still "1.3.0-27.2" in the POM here: 
[https://github.com/jiayuasu/geotools-wrapper/blob/main/pom.xml]

> 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)

Reply via email to