[
https://issues.apache.org/jira/browse/LUCENE-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13221174#comment-13221174
]
David Smiley commented on LUCENE-3795:
--------------------------------------
Everything depends on something. Lucene depends on Java, and it has no control
over Java except to complain when there are bugs. This module isn't the first
module to have a dependency and frankly I don't understand the aversion to them
-- it's a natural thing. I agree you can have too many.
I think Lucene-Spatial's dependency on Spatial4j represents the *best* type of
a dependency that Lucene/Solr could have:
# ASL licensed
# Has code & tests there that aren't related to Lucene; don't clutter or
diffuse scope of Lucene's codebase.
# Strong relationship to Lucene/Solr. Put another way, if Spatial4j were a
product, it's only customer right now is Lucene/Solr. Consequently:
## When Lucene/Solr decides to release a version, Spatial4J committers will do
the same. No SNAPSHOT dependency from a Lucene release.
## When a bug or feature request comes up via Lucene that requires changes in
Spatial4J, you (a Lucene committer) can coordinate these changes with great
efficiency given that you know Spatial4J committers.
## You can become a committer on Spatial4j with far less time than it took me
to become a committer here, I swear ;-) -- _especially_ the spatial-minded
folks: Chris (if we had your GitHub username, you'd be grandfathered in), Uwe,
Grant, Yonik?
And because it's a dependency and not 1st-party code, it has a greater
opportunity to receive improvements from outside parties since it's a smaller
project with a more focused committer pool. This stuff has nothing to do with
Lucene, remember.
> Replace spatial contrib module with LSP's spatial-lucene module
> ---------------------------------------------------------------
>
> Key: LUCENE-3795
> URL: https://issues.apache.org/jira/browse/LUCENE-3795
> 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:
> http://code.google.com/p/lucene-spatial-playground/ 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
