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

Steve Rowe commented on LUCENE-6997:
------------------------------------

Okay, I'll watch LUCENE-7015.

{quote}
bq. ...you didn't modify any inter-module dependencies in other POM templates, 
and I'm pretty sure there are several changes to make (looking at the Ant and 
IntelliJ build changes you made).
This (and ant) is where I'll likely need to most help. Re: maven I only ran ant 
generate-maven-artifacts and it was happy. But that doesn't mean I didn't miss 
other unhappy targets.
{quote}

I forgot about the maven intermodule dependencies that these should be picked 
up automatically when the POM templates are filled out.  There is one exception 
though: dependencies on other modules' tests is not checked for, so when 
modules need this, we modify the depended-on module's POM to build a test-jar, 
which is then manually added to the depending module.  I'll take care of it.

> Graduate GeoUtils and postings based GeoPointField from sandbox...
> ------------------------------------------------------------------
>
>                 Key: LUCENE-6997
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6997
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: modules/spatial
>            Reporter: Nicholas Knize
>             Fix For: 5.5, trunk
>
>         Attachments: LUCENE-6997.patch
>
>
> {{GeoPointField}} is a lightweight dependency-free postings based geo field 
> currently in sandbox. It has evolved into a very fast lightweight geo option 
> that heavily leverages the optimized performance of the postings structure. 
> It was originally intended to graduate to core but this does not seem 
> appropriate given the variety of "built on postings" term encoding options 
> (e.g., see LUCENE-6930).  
> Additionally, the {{Geo*Utils}} classes are dependency free lightweight 
> relational approximation utilities used by both {{GeoPointField}} and the BKD 
> based {{LatLonField}} and can also be applied to benefit the lucene-spatial 
> module.
> These classes have been evolving and baking for some time and are at a 
> maturity level qualifying for promotion from sandbox. This will allow support 
> for experimental encoding methods with (minimal) backwards compatibility - 
> something sandbox does not allow.
> Since GeoPoint classes are dependency free, all GeoPointField and support and 
> utility classes currently in sandbox would be promoted to the spatial3d 
> package. (possibly a separate issue to rename spatial3d to spatialcore or 
> spatiallite?) Such that for basic lightweight Geo support one would only need 
> a handful of lucene jars. By simply adding the lucene-spatial module and its 
> dependency jars users can obtain more advanced geospatial support (heatmap 
> facets, full shape relations, etc).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to