dependabot[bot] opened a new pull request, #24:
URL: https://github.com/apache/opennlp-addons/pull/24

   Bumps [com.spatial4j:spatial4j](https://github.com/locationtech/spatial4j) 
from 0.4.1 to 0.5.
   <details>
   <summary>Changelog</summary>
   <p><em>Sourced from <a 
href="https://github.com/locationtech/spatial4j/blob/master/CHANGES.md";>com.spatial4j:spatial4j's
 changelog</a>.</em></p>
   <blockquote>
   <h2>VERSION 0.5</h2>
   <p>DATE: 18 September 2015</p>
   <h3>User/API changes &amp; Notes:</h3>
   <ul>
   <li>
   <p><a 
href="https://redirect.github.com/locationtech/spatial4j/issues/96";>#96</a>: 
Java 1.7 is now the minimum version supported by Spatial4j.</p>
   </li>
   <li>
   <p>Spatial4j supports more formats now; see &quot;FORMATS.md&quot;.  More 
info below.</p>
   </li>
   <li>
   <p><a 
href="https://redirect.github.com/locationtech/spatial4j/issues/107";>#107</a>: 
The DatelineRule and ValidationRule enums were moved to the 
com.spatial4j.context.jts package, and the
   current setting is exposed on JtsSpatialContext. The autoIndex boolean was 
moved there too.
   These things used to be defined in JtsWktShapeParser. (Justin Deoliveira 
&amp; David Smiley)</p>
   </li>
   <li>
   <p><a 
href="https://redirect.github.com/locationtech/spatial4j/issues/92";>#92</a>: 
Shape now exposes the SpatialContext</p>
   </li>
   <li>
   <p>Given a JTS Geometry instance and the desire to have a Spatial4j 
equivalent Shape, consider
   using JtsSpatialContext.createShapeFromGeometry(geometry) vs. 
makeShape(geometry).  See the
   javadocs.</p>
   </li>
   <li>
   <p>WktShapeParser was renamed to WKTReader, although WktShapeParser still 
exists as a deprecated
   subclass of WKTReader.  SpatialContext.getWktShapeParser returns WKTReader.  
JtsWktShapeParser
   was renamed to JtsWKTReader.</p>
   </li>
   <li>
   <p><a 
href="https://redirect.github.com/locationtech/spatial4j/issues/90";>#90</a>: 
Publish the test-jar. (Nick Knize)</p>
   </li>
   <li>
   <p>The internal class &quot;Range&quot; is deprecated, unused, and will be 
removed in a future release.</p>
   </li>
   </ul>
   <h3>Features:</h3>
   <ul>
   <li>
   <p><a 
href="https://redirect.github.com/locationtech/spatial4j/issues/91";>#91</a>: 
SpatialContext.getFormats() returns a new SupportedFormats which lists the 
supported
   Shape formats for readers &amp; writers.  (Ryan McKinley)</p>
   </li>
   <li>
   <p><a 
href="https://redirect.github.com/locationtech/spatial4j/issues/94";>#94</a>: 
WKT writing support. (Ryan McKinley)</p>
   </li>
   <li>
   <p><a 
href="https://redirect.github.com/locationtech/spatial4j/issues/94";>#94</a>: 
GeoJSON format support; both reading &amp; writing. (Ryan McKinley, Justin 
Deoliveira)</p>
   </li>
   <li>
   <p><a 
href="https://redirect.github.com/locationtech/spatial4j/issues/117";>#117</a>: 
Polyshape format support; both reading &amp; writing. (Ryan McKinley, Justin 
Deoliveira)</p>
   </li>
   <li>
   <p><a 
href="https://redirect.github.com/locationtech/spatial4j/issues/98";>#98</a>: 
SpatialPredicate class -- moved from Lucene Spatial. (Ryan McKinley)</p>
   </li>
   </ul>
   <h3>Improvements:</h3>
   <ul>
   <li>
   <p><a 
href="https://redirect.github.com/locationtech/spatial4j/issues/103";>#103</a>: 
JtsGeometry now accepts GeometryCollection if it's component geometry types are
   homogeneous. (Justin Deoliveira)<br />
   note: for non-homogeneous ones, see 
JtsSpatialContext.createShapeFromGeometry</p>
   </li>
   <li>
   <p><a 
href="https://redirect.github.com/locationtech/spatial4j/issues/97";>#97</a>: 
More consistent use of ParseException vs InvalidShapeException (Ryan 
McKinley)</p>
   </li>
   </ul>
   <h3>Bugs:</h3>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/locationtech/spatial4j/commit/08ba0f4b6b9abe533cd287f291522dbfdd5e6531";><code>08ba0f4</code></a>
 [maven-release-plugin] prepare release spatial4j-0.5</li>
   <li><a 
href="https://github.com/locationtech/spatial4j/commit/6a908988898abc875498c879ad7bc34cbea79559";><code>6a90898</code></a>
 Remove about.md &amp; notice.md from release branch. Clarify which is the 
license...</li>
   <li><a 
href="https://github.com/locationtech/spatial4j/commit/52132dde324b209e60159125d26e85812f8662bb";><code>52132dd</code></a>
 [maven-release-plugin] rollback the release of spatial4j-0.5</li>
   <li><a 
href="https://github.com/locationtech/spatial4j/commit/2c784cfd9de2c542ae75354b13b2721eb86502b6";><code>2c784cf</code></a>
 [maven-release-plugin] prepare for next development iteration</li>
   <li><a 
href="https://github.com/locationtech/spatial4j/commit/c7ae72c23a18c20c89cdf0bdb75d4550e75068a3";><code>c7ae72c</code></a>
 [maven-release-plugin] prepare release spatial4j-0.5</li>
   <li><a 
href="https://github.com/locationtech/spatial4j/commit/c3138ce724d7d9ff4e73a0a76d60344864944ab0";><code>c3138ce</code></a>
 Update pom.xml (minor):</li>
   <li><a 
href="https://github.com/locationtech/spatial4j/commit/b4c9f497adef25e3876e2b61e7c893404a4f4cee";><code>b4c9f49</code></a>
 Update 0.5 release date to today.</li>
   <li><a 
href="https://github.com/locationtech/spatial4j/commit/fcf4083ef2197b614a2ac0f372ff129d580c7bf7";><code>fcf4083</code></a>
 Merge pull request <a 
href="https://redirect.github.com/locationtech/spatial4j/issues/124";>#124</a> 
from locationtech/RoundTripIssues</li>
   <li><a 
href="https://github.com/locationtech/spatial4j/commit/4910c70642387e30b22e07e81327d73d9dfb6bc2";><code>4910c70</code></a>
 Update FORMATS.md</li>
   <li><a 
href="https://github.com/locationtech/spatial4j/commit/14d2c82734d8994051630a48456bcd0e6cfdee38";><code>14d2c82</code></a>
 Test IO RoundTrip: by default always check equality</li>
   <li>Additional commits viewable in <a 
href="https://github.com/locationtech/spatial4j/compare/spatial4j-0.4.1...spatial4j-0.5";>compare
 view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=com.spatial4j:spatial4j&package-manager=maven&previous-version=0.4.1&new-version=0.5)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   <details>
   <summary>Dependabot commands and options</summary>
   <br />
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@dependabot show <dependency name> ignore conditions` will show all of 
the ignore conditions of the specified dependency
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   
   
   </details>


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to