lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-3795) Replace spatial contrib module with LSP's spatial-lucene module
Date Fri, 02 Mar 2012 14:23:57 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220948#comment-13220948
] 

David Smiley commented on LUCENE-3795:
--------------------------------------

Commons-lang is used by both Spatial4J and the new spatial-module.  This dependency can easily
be severed and will happen shortly.

SLF4j is used by both Spatial4J and the new spatial-module. I really like SLF4J but all this
resistance to remove dependencies leads me to compromise, and I'll find a way to removing
it or have it as an optional dependency.

Uwe and others, the rationale for a core spatial library off of Lucene is my last (long) comment:
https://issues.apache.org/jira/browse/LUCENE-3795?focusedCommentId=13216522&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13216522
For what its worth, Ryan and I absolutely love the plan for all of the points in it.  I wish
someone had expressed their dissenting opinion on it at that time -- From Ryan and I's perspective
there basically isn't anything not to like.  Can anything be done to warm people up to this?

Rob; you're absolutely right that there needs to be a release tagged in the Spatial4J repo.
 Ryan has already taken steps to get this library in published Maven repos which is the most
meaningful step that could be taken to officially release it.  Again, we should certainly
tag it because it is both best practice and easy.

The ASF is a bit heavy on process and less permissive on interactions with LGPL dependencies
(even optional ones?) and so I don't think ASF/incubator is a good place for Spatial4j as
an independent project.  As frustrating as I find it, the making of spatial-4j _could_ be
reverted, returning back to the 2-module setup that some people here seemed to express resistance
to.
                
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message