[
https://issues.apache.org/jira/browse/LUCENE-7152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220981#comment-15220981
]
Robert Muir commented on LUCENE-7152:
-------------------------------------
Just wasted some fun time fighting the build system because my patch in
LUCENE-7153 exposes a class in a sandbox/ public api from spatial/
These kinds of things are important to think about when considering "spatial
module madness" versus just e.g. having 5 key classes in core. It is not just
harder on the user, it is harder on us too. Fortunately, I know the necessary
voodoo.
> Refactor lucene-spatial GeoUtils to core
> ----------------------------------------
>
> Key: LUCENE-7152
> URL: https://issues.apache.org/jira/browse/LUCENE-7152
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Nicholas Knize
> Attachments: LUCENE-7152.patch
>
>
> {{GeoUtils}} contains a lot of common spatial mathematics that can be reused
> across multiple packages. As discussed in LUCENE-7150 this issue will
> refactor GeoUtils to a new {{o.a.l.util.geo}} package in core that can be the
> home for other reusable spatial utility classes required by field and query
> implementations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
