[
https://issues.apache.org/jira/browse/LUCENE-8161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16354970#comment-16354970
]
David Smiley commented on LUCENE-8161:
--------------------------------------
Based on our docs in LicenseType, the right one to use in this case is BSD_LIKE.
Lucene CHANGES.txt:
{noformat}
Other
* LUCENE-8616: spatial-extras: the Spatial4j dependency has been updated from
0.6 to 0.7,
which is drop-in compatible (Lucene doesn't expressly use any of the few API
differences).
Spatial4j 0.7 is compatible with JTS 1.15.0 and not any prior version. JTS
1.15.0 is
dual-licensed to include BSD; prior versions were LGPL. (David Smiley)
{noformat}
I'll file a follow-up issue for Solr.
> Update to Spatial4j 0.7 (to support JTS 1.15)
> ---------------------------------------------
>
> Key: LUCENE-8161
> URL: https://issues.apache.org/jira/browse/LUCENE-8161
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/spatial-extras
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Major
> Attachments: LUCENE-8161_Spatial4j_0_7_and_add_JTS_1_15_0.patch
>
>
> Spatial4j 0.7 was released late December 2017, principally with support for
> JTS 1.15. There are some other changes less pertinent to Lucene/Solr but
> I'll refer to the change list:
> [https://github.com/locationtech/spatial4j/blob/spatial4j-0.7/CHANGES.md]
> This JTS release has an API breakage in that the package root was changed
> from {{com.vividsolutions}} to {{org.locationtech}} but should otherwise be
> compatible. JTS is now dual-licensed as EPL 1.0 and EDL 1.0 (a BSD style
> 3-clause license). This JTS release also included various improvements,
> including faster LineString intersection. That performance improvement was
> found in the context of Lucene spatial-extras real-world use.
> Anyone using JTS with lucene-spatial-extras will be forced to update to JTS
> 1.15. I'd like to add a test dependency from lucene-spatial-extras to JTS
> (the BSD licensed version of course) as there is at least one test with a
> JUnit "assumeTrue" on it being on the classpath – JtsPolygonTest.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]