Re: [PR] [CI] Address the race condition among multiple CI deploying to the website branch [sedona]
jiayuasu merged PR #1318: URL: https://github.com/apache/sedona/pull/1318 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [CI] Address the race condition among multiple CI deploying to the website branch [sedona]
jiayuasu opened a new pull request, #1318: URL: https://github.com/apache/sedona/pull/1318 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - No, this is a documentation update. The PR name follows the format `[DOCS] my subject`. ## What changes were proposed in this PR? Prepull the website branch before deploying to the website branch, as recommended by https://github.com/jimporter/mike ## How was this patch tested? Tested in the CI ## Did this PR include necessary documentation updates? - No, this PR does not affect any public API so no need to change the documentation. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [DOCS] Fix grammar in the `pull_request_template.md` [sedona]
jiayuasu merged PR #1316: URL: https://github.com/apache/sedona/pull/1316 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-529] Add basic `EditorConfig` file [sedona]
jiayuasu merged PR #1315: URL: https://github.com/apache/sedona/pull/1315 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-528] Add `pre-commit` hook `check-yaml` [sedona]
jiayuasu merged PR #1313: URL: https://github.com/apache/sedona/pull/1313 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [DOCS] Fix Markdown links to also work on GitHub [sedona]
jiayuasu merged PR #1317: URL: https://github.com/apache/sedona/pull/1317 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [DOCS][CI] upgrade `actions/setup-java` to `v4` [sedona]
jiayuasu merged PR #1309: URL: https://github.com/apache/sedona/pull/1309 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [DOCS] Fix grammar and spelling in `docs/setup/cluster.md` [sedona]
jiayuasu merged PR #1310: URL: https://github.com/apache/sedona/pull/1310 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] sedona-vis for 1.5.1 ? [sedona]
JimShady closed issue #1312: sedona-vis for 1.5.1 ? URL: https://github.com/apache/sedona/issues/1312 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Community over Code EU 2024: Start planning your trip!
[Note: You're receiving this email because you are subscribed to one or more project dev@ mailing lists at the Apache Software Foundation.] Dear community, We hope you are doing great, are you ready for Community Over Code EU? Check out the featured sessions, get your tickets with special discounts and start planning your trip. Save your spot! Take a look at our lineup of sessions, panelists and featured speakers and make your final choice: * EU policies and regulations affecting open source specialists working in OSPOs The panel will discuss how EU legislation affects the daily work of open source operations. Panelists will cover some recent policy updates, the challenges of staying compliant when managing open source contribution and usage within organizations, and their personal experiences in adapting to the changing European regulatory environment. * Doing for sustainability, what open source did for software In this keynote Asim Hussain will explain the history of Impact Framework, a coalition of hundreds of software practitioners with tangible solutions that directly foster meaningful change by measuring the environmental impacts of a piece of software. Don’t forget that we have special discounts for groups, students and Apache committers. Visit the website to discover more about these rates.[1] It's time for you to start planning your trip. Remember that we have prepared a “How to get there” guide that will be helpful to find out the best transportation, either train, bus, flight or boat to Bratislava from wherever you are coming from. Take a look at the different options and please reach out to us if you have any questions. We have available rooms -with a special rate- at the Radisson Blu Carlton Hotel, where the event will take place and at the Park Inn Hotel which is only 5 minutes walking from the venue. [2] However, you are free to choose any other accommodation options around the city. See you in Bratislava, Community Over Code EU Team [1]: https://eu.communityovercode.org/tickets/ "Register" [2]: https://eu.communityovercode.org/venue/ "Where to stay"
[PR] [DOCS] Fix Markdown links to also work on GitHub [sedona]
jbampton opened a new pull request, #1317: URL: https://github.com/apache/sedona/pull/1317 ## Did you read the Contributor Guide? - Yes, I have read [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - No, this is a documentation update. The PR name follows the format `[DOCS] my subject`. ## What changes were proposed in this PR? If you go to the next link / page on the GitHub website and see the link `RS_NetCDFInfo` just below you will find after clicking that the link is wrong it jumps away from the page. https://github.com/apache/sedona/blob/master/docs/api/sql/Raster-loader.md#rs_fromnetcdf And you can see it working here: https://github.com/jbampton/sedona/blob/fix-links-to-work-on-github/docs/api/sql/Raster-loader.md#rs_fromnetcdf Same with the other three links that were fixed. They all now work on GitHub too. ## How was this patch tested? Visually and clicked the links on GitHub ## Did this PR include necessary documentation updates? - No, this PR does not affect any public API so no need to change the docs. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Participate in the ASF 25th Anniversary Campaign
Hi everyone, As part of The ASF’s 25th anniversary campaign[1], we will be celebrating projects and communities in multiple ways. We invite all projects and contributors to participate in the following ways: * Individuals - submit your first contribution: https://news.apache.org/foundation/entry/the-asf-launches-firstasfcontribution-campaign * Projects - share your public good story: https://docs.google.com/forms/d/1vuN-tUnBwpTgOE5xj3Z5AG1hsOoDNLBmGIqQHwQT6k8/viewform?edit_requested=true * Projects - submit a project spotlight for the blog: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=278466116 * Projects - contact the Voice of Apache podcast (formerly Feathercast) to be featured: https://feathercast.apache.org/help/ * Projects - use the 25th anniversary template and the #ASF25Years hashtag on social media: https://docs.google.com/presentation/d/1oDbMol3F_XQuCmttPYxBIOIjRuRBksUjDApjd8Ve3L8/edit#slide=id.g26b0919956e_0_13 If you have questions, email the Marketing & Publicity team at mark...@apache.org. Peace, BKP [1] https://apache.org/asf25years/ [NOTE: You are receiving this message because you are a contributor to an Apache Software Foundation project. The ASF will very occasionally send out messages relating to the Foundation to contributors and members, such as this one.] Brian Proffitt VP, Marketing & Publicity VP, Conferences
Re: Report from last week OGC meeting
Thank you, Martin! On Wed, Apr 3, 2024 at 04:22 Martin Desruisseaux < martin.desruisse...@geomatys.com> wrote: > Hello all > > The Open Geospatial Consortium (OGC) had a meeting last week in Delft, > Netherlands. Over 300 people attended in person, and 100+ online. A > subset (315 slides) of the presentations is available at [1], and a > shorter subset (38 slides) at [2]. The next sections in this email are a > mix of personal notes and copies of a template written by OGC staff in [3]. > > [1]https://portal.ogc.org/files/?artifact_id=107819 > [2]https://portal.ogc.org/files/?artifact_id=107799 > [3]https://portal.ogc.org/files/?artifact_id=107820 > > > OGC Web Services to OGC API transition > > The full set of capabilities offered by the OGC Web Services Standards > (e.g., Web Map Service (WMS), Web Feature Service (WFS), etc.) have now > been reflected in published OGC API Standards or in work in or > approaching final approval vote. For example, OGC API – Maps – Part 1 > can be a replacement for WMS (see [1] for more details). Feature API – > part 3 – filtering and CQL2 are going to vote. Over the coming months, > OGC will establish a process and resources to aid in transition to the > more modern Standards, while still ensuring that the user community > recognizes that the legacy web services are still functional and valuable. > > > Changes proposal for Referencing by Coordinates > > One of the mean services of Apache Spatial Information System (SIS) is > its implementation of ISO 19111 / OGC Topic 2 (Referencing by > Coordinates). Apache SIS has been used during OGC TestBed last summer > for prototyping the use of ISO 19111 / OGC Topic 2 standards in space > and for planets other than Earth. The experience gained has been used > for proposing changes to the existing standards: addition of a new > CelestialBody class for identifying the planet, addition of a new > MinkowskiCS class for use with Einstein's special relativity, > generalization of some existing properties, etc. Since the change > proposals concern a joint standard between OGC and ISO, and since ISO is > already revising ISO 19111 with their own changes right now, a > discussion was about how to move forward in sync with ISO. Current > consensus is to start this work at OGC first (as we did for previous > revisions). > > Another discussion was about how to move forward with a standard JSON > encoding of Coordinate Reference Systems (CRS). The PROJ project > proposed their own encoding, named PROJJSON. This encoding is a > translation of Well-Known Text (WKT) encoding, with a one-by-one > matching. But WKT is not a model, it is an encoding derived from the > model described in ISO 19111, and is not a one-by-one mapping of that > model. Currently, the only encoding covering fully the ISO 19111 model > is the Geographic Markup Language (GML), but that encoding is based on > an older version of ISO 19111. The working group plans to use PROJJSON > as a starting point, but if we want JSON to replace GML, we may need to > modify or extend PROJJSON. The group will try to avoid gratuitous > incompatible changes, but I think that some changes should be expected. > > > Other sync between OGC and ISO standards > > Temporal reference systems were used to be defined in a separated > standard, ISO 19108. However this standard, published in 2002, does not > fit very well in current OGC/ISO standards. Part of its material has > been absorbed in latest revision of above-cited ISO 19111. The remaining > parts were discussed in a separated OGC working group and resulted in a > new abstract model, which is going to electronic vote soon. My > understanding is that ISO 19108 will no longer be used and will be > replaced by the new OGC abstract topic, with no direct equivalence on > ISO side. > > ISO 19123-1 and ISO 19123-3 are two abstract specifications, for > coverage and for processing respectively. They were adopted in April > 2023 and became OGC Topic 6. The ISO/OGC relationship is similar to what > has been done with ISO 19111 / OGC Topic 2: the OGC abstract topic has > the same content as the ISO standard, with only editorial differences > (mostly formatting). ISO 19123-3 defines coverage constructors (how to > build a coverage from scratch or derive from an existing coverage), > coverage condensers (summary information from a coverage) and an > expression language. ISO 19123-4 is currently in development and will be > about tiling. See [1] for more overview. > > OGC topic 1 – spatial schema (ISO 19107) has a convoluted history. It > was an OGC abstract topic, then dropped, but will now come bask as topic > 0. Number 0 is used because number 1 is already used for something > different now. > > > Moving features / GeoAPI / OpenEO > > The working group has defined an abstract model, which is now moving to > the vote state at OGC. This model is strongly inspired by the Moving > Feature JSON encoding, but also introduces some new
[PR] [DOCS] Fix grammar in the `pull_request_template.md` [sedona]
jbampton opened a new pull request, #1316: URL: https://github.com/apache/sedona/pull/1316 ## Did you read the Contributor Guide? - Yes, I have read [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - No, this is a documentation update. The PR name follows the format `[DOCS] my subject`. ## What changes were proposed in this PR? Cleaned up the pull request template. ## How was this patch tested? Just by reading the new better version. ## Did this PR include necessary documentation updates? - No, this PR does not affect any public API so no need to change the docs. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-529] Add basic `EditorConfig` file [sedona]
jbampton opened a new pull request, #1315: URL: https://github.com/apache/sedona/pull/1315 ## Did you read the Contributor Guide? - Yes, I have read [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-529. The PR name follows the format `[SEDONA-XXX] my subject`. ## What changes were proposed in this PR? This PR adds a basic `.editorconfig` file. Most editors / IDEs already have support for editor config. https://editorconfig.org/ https://github.com/editorconfig/editorconfig/wiki/Projects-Using-EditorConfig "What is EditorConfig? EditorConfig helps maintain consistent coding styles for multiple developers working on the same project across various editors and IDEs. The EditorConfig project consists of a file format for defining coding styles and a collection of text editor plugins that enable editors to read the file format and adhere to defined styles. EditorConfig files are easily readable and they work nicely with version control systems." ## How was this patch tested? ## Did this PR include necessary documentation updates? - No, this PR does not affect any public API so no need to change the docs. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (SEDONA-529) Add basic `EditorConfig` file
John Bampton created SEDONA-529: --- Summary: Add basic `EditorConfig` file Key: SEDONA-529 URL: https://issues.apache.org/jira/browse/SEDONA-529 Project: Apache Sedona Issue Type: New Feature Reporter: John Bampton -- This message was sent by Atlassian Jira (v8.20.10#820010)
[I] Suggested edit to documentation [sedona]
JimShady opened a new issue, #1314: URL: https://github.com/apache/sedona/issues/1314 https://sedona.apache.org/1.5.1/api/sql/Raster-loader/#rs_makeemptyraster When making a global raster using, for example, WGS84, the pixel size on the y axis should be specified as a negative number. I think this is a 'gotcha' and should be explicitly explained? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-528] Add `pre-commit` hook `check-yaml` [sedona]
jbampton opened a new pull request, #1313: URL: https://github.com/apache/sedona/pull/1313 ## Did you read the Contributor Guide? - Yes, I have read [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-528. The PR name follows the format `[SEDONA-XXX] my subject`. ## What changes were proposed in this PR? Added another hook to our pre-commit framework. ## How was this patch tested? Ran locally: `pre-commit run --all-files` ## Did this PR include necessary documentation updates? - No, this PR does not affect any public API so no need to change the docs. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (SEDONA-528) Add `pre-commit` hook `check-yaml`
John Bampton created SEDONA-528: --- Summary: Add `pre-commit` hook `check-yaml` Key: SEDONA-528 URL: https://issues.apache.org/jira/browse/SEDONA-528 Project: Apache Sedona Issue Type: Test Reporter: John Bampton -- This message was sent by Atlassian Jira (v8.20.10#820010)
[I] Sedona-via for 1.5.1 ? [sedona]
JimShady opened a new issue, #1312:
URL: https://github.com/apache/sedona/issues/1312
I am updating our Databricks init script for apache-sedona 1.5.1. This is my
attempt:
```
#!/bin/bash
# Install Apache Sedona
# Reference https://sedona.apache.org/setup/databricks/
# On cluster startup, this script downloads the dependencies from Maven into
DBFS,
# copies the Sedona jars to the cluster's default jar directory
cat < /databricks/driver/conf/01-custom-spark-driver-defaults.conf
[driver] {
"spark.serializer" = "org.apache.spark.serializer.KryoSerializer"
"spark.kryo.registrator" =
"org.apache.sedona.core.serde.SedonaKryoRegistrator"
"spark.sql.extensions" =
"org.apache.sedona.viz.sql.SedonaVizExtensions,org.apache.sedona.sql.SedonaSqlExtensions"
"sedona.global.index" = "true"
"sedona.global.indextype" = "quadtree"
"sedona.join.gridtype" = "kdbtree"
"spark.databricks.io.cache.enabled" = "true"
"spark.sql.execution.arrow.enabled" = "false"
"sedona.global.charset" = "utf8"
}
EOF
# Create JAR directory for Sedona
mkdir -p /dbfs/FileStore/jars/sedona/1.5.1
# Download the dependencies from Maven into DBFS
curl -o /dbfs/FileStore/jars/sedona/1.5.1/geotools-wrapper-1.5.1-28.2.jar
"https://repo1.maven.org/maven2/org/datasyslab/geotools-wrapper/1.5.1-28.2/geotools-wrapper-1.5.1-28.2.jar;
curl -o
/dbfs/FileStore/jars/sedona/1.5.1/sedona-spark-shaded-3.4_2.12-1.5.1.jar
"https://repo1.maven.org/maven2/org/apache/sedona/sedona-spark-shaded-3.4_2.12/1.5.1/sedona-spark-shaded-3.4_2.12-1.5.1.jar;
curl -o /dbfs/FileStore/jars/sedona/1.5.1/sedona-viz-3.0_2.12-1.5.0.jar
"https://repo1.maven.org/maven2/org/apache/sedona/sedona-viz-3.0_2.12/1.5.0/sedona-viz-3.0_2.12-1.5.0.jar;
# Copy the Sedona jars to the cluster's default jar directory.
cp /dbfs/FileStore/jars/sedona/1.5.1/*.jar /databricks/jars
python -m pip install --upgrade pip
pip install apache-sedona
```
I am unsure about this line:
`curl -o /dbfs/FileStore/jars/sedona/1.5.1/sedona-viz-3.0_2.12-1.5.0.jar
"https://repo1.maven.org/maven2/org/apache/sedona/sedona-viz-3.0_2.12/1.5.0/sedona-viz-3.0_2.12-1.5.0.jar"`
Because there does not seem to be sedona-viz for 1.5.1? What should I put
here, or should I just remove it?
Thanks.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[PR] [SEDONA-527] Add `pre-commit` hook `check-json`; Lint JSON files [sedona]
jbampton opened a new pull request, #1311: URL: https://github.com/apache/sedona/pull/1311 ## Did you read the Contributor Guide? - Yes, I have read [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-527. The PR name follows the format `[SEDONA-XXX] my subject`. ## What changes were proposed in this PR? Added another hook to our pre-commit framework: https://github.com/pre-commit/pre-commit-hooks?tab=readme-ov-file#check-json ## How was this patch tested? With the new hook `check-json` added I first ran locally: `pre-commit run --all-files` which showed the JSON files that weren't valid JSON. Then checked some JSON with JSON Lint online. https://jsonlint.com/ Then fixed the JSON to be valid JSON. ## Did this PR include necessary documentation updates? - No, this PR does not affect any public API so no need to change the docs. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (SEDONA-527) Add `pre-commit` hook `check-json`; Lint JSON files
John Bampton created SEDONA-527: --- Summary: Add `pre-commit` hook `check-json`; Lint JSON files Key: SEDONA-527 URL: https://issues.apache.org/jira/browse/SEDONA-527 Project: Apache Sedona Issue Type: Test Reporter: John Bampton -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] [DOCS] Fix grammar and spelling in `docs/setup/cluster.md` [sedona]
jbampton opened a new pull request, #1310: URL: https://github.com/apache/sedona/pull/1310 ## Did you read the Contributor Guide? - Yes, I have read [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - No, this is a documentation update. The PR name follows the format `[DOCS] my subject`. ## What changes were proposed in this PR? Fixed some grammar and spelling. ## How was this patch tested? ## Did this PR include necessary documentation updates? - No, this PR does not affect any public API so no need to change the docs. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [DOCS][CI] upgrade `actions/setup-java` to `v4` [sedona]
jbampton opened a new pull request, #1309: URL: https://github.com/apache/sedona/pull/1309 ## Did you read the Contributor Guide? - Yes, I have read [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - No, this is a documentation update. The PR name follows the format `[DOCS] my subject`. ## What changes were proposed in this PR? Upgraded actions/setup-java to v4. ## How was this patch tested? ## Did this PR include necessary documentation updates? - No, this PR does not affect any public API so no need to change the docs. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [DOCS][CI] Auto push docs to the website branch [sedona]
jiayuasu merged PR #1305: URL: https://github.com/apache/sedona/pull/1305 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-526] Upgrade `actions/setup-java` to `v4` [sedona]
jiayuasu merged PR #1308: URL: https://github.com/apache/sedona/pull/1308 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [DOCS] Complete the README TOC [sedona]
jiayuasu merged PR #1307: URL: https://github.com/apache/sedona/pull/1307 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-526] Upgrade `actions/setup-java` to `v4` [sedona]
jbampton opened a new pull request, #1308: URL: https://github.com/apache/sedona/pull/1308 ## Did you read the Contributor Guide? - Yes, I have read [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-526. The PR name follows the format `[SEDONA-XXX] my subject`. ## What changes were proposed in this PR? Upgraded to actions/setup-java version 4. "The major breaking change in V2 is the new mandatory distribution input." "Use the zulu keyword if you would like to continue using the same distribution as in V1." https://github.com/actions/setup-java/blob/main/docs/switching-to-v2.md ## How was this patch tested? ## Did this PR include necessary documentation updates? - No, this PR does not affect any public API so no need to change the docs. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (SEDONA-526) Upgrade `actions/setup-java` to `v4`
John Bampton created SEDONA-526: --- Summary: Upgrade `actions/setup-java` to `v4` Key: SEDONA-526 URL: https://issues.apache.org/jira/browse/SEDONA-526 Project: Apache Sedona Issue Type: Task Reporter: John Bampton -- This message was sent by Atlassian Jira (v8.20.10#820010)
