lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan McKinley (Commented) (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3795) Replace spatial contrib module with LSP's spatial-lucene module
Date Fri, 02 Mar 2012 17:59:59 GMT


Ryan McKinley commented on LUCENE-3795:

bq. What's the reason to have spatial4j outside of Lucene?

1. Making JTS a 1st class test object (also why SIS is not an option)
2. The spatial4j.jar is useful on its own -- it has a chance to build its own community. 
3. Lucene is not a great dev community for things that are not primarily lucene focused.

I understand my primary concern (JTS) is a non issue for many people here -- The trade off
to have compile/test dependencies on JTS isn't an option at ASF.

I like this option because it gives lucene a solid ASL solution to support most things.  *If*
people want to add JTS to their runtime, they then get strong polygon support.

The alternative packaging structure gets pretty crazy:

In ASF Lucene Reps:
* modules/spatial-base (no lucene dependencies)
* modules/spatial-strategies (uses base)
* solr/spatial...

* spatial-base-jts (base with JTS) 
* spatial-strategies-with-jts
* spatial-solr-with-jts

If I want to make sure the JtsSpatialContext passes all the *same* tests that the SimpleSpatialContext
passes, the structure gets even crazier because we have to package the test projects too!


bq. We all agreed modules should be treated like lucene core

hymmm -- my understanding is that modules have *flexibility* to have dependencies that are


> Replace spatial contrib module with LSP's spatial-lucene module
> ---------------------------------------------------------------
>                 Key: LUCENE-3795
>                 URL:
>             Project: Lucene - Java
>          Issue Type: New Feature
>          Components: modules/spatial
>            Reporter: David Smiley
>            Assignee: David Smiley
>             Fix For: 4.0
> I propose that Lucene's spatial contrib module be replaced with the spatial-lucene module
within Lucene Spatial Playground (LSP).  LSP has been in development for approximately 1 year
by David Smiley, Ryan McKinley, and Chris Male and we feel it is ready.  LSP is here:
 and the spatial-lucene module is intuitively in svn/trunk/spatial-lucene/.
> I'll add more comments to prevent the issue description from being too long.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message