You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Smiley (JIRA)" <ji...@apache.org> on 2016/03/08 05:43:40 UTC
[jira] [Updated] (LUCENE-7056) Separate Geo3DPoint into another
package from the rest of Geo3D
[ https://issues.apache.org/jira/browse/LUCENE-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Smiley updated LUCENE-7056:
---------------------------------
Description:
The original description follows; it's greater in scope than the new title:
----
This is a proposal for the "spatial3d" module to be purely about the shape/geometry implementations it has. In Lucene 5 that's actually all it has. In Lucene 6 at the moment its ~76 files have 2 classes that I think should go elsewhere: Geo3DPoint and PointInGeo3DShapeQuery. Specifically lucene-spatial-extras (which doesn't quite exist yet so lucene-spatial) would be a suitable place due to the dependency. _Eventually_ I see this module migrating elsewhere be it on its own or a part of something else more spatial-ish. Even if that never comes to pass, non-Lucene users who want to use this module for it's geometry annoyingly have to exclude the Lucene dependencies that are there because this module also contains these two classes.
In a comment I'll suggest some specifics.
was:
This is a proposal for the "spatial3d" module to be purely about the shape/geometry implementations it has. In Lucene 5 that's actually all it has. In Lucene 6 at the moment its ~76 files have 2 classes that I think should go elsewhere: Geo3DPoint and PointInGeo3DShapeQuery. Specifically lucene-spatial-extras (which doesn't quite exist yet so lucene-spatial) would be a suitable place due to the dependency. _Eventually_ I see this module migrating elsewhere be it on its own or a part of something else more spatial-ish. Even if that never comes to pass, non-Lucene users who want to use this module for it's geometry annoyingly have to exclude the Lucene dependencies that are there because this module also contains these two classes.
In a comment I'll suggest some specifics.
Summary: Separate Geo3DPoint into another package from the rest of Geo3D (was: Spatial3d/Geo3d should have zero runtime dependencies)
> Separate Geo3DPoint into another package from the rest of Geo3D
> ---------------------------------------------------------------
>
> Key: LUCENE-7056
> URL: https://issues.apache.org/jira/browse/LUCENE-7056
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/spatial3d
> Reporter: David Smiley
> Assignee: David Smiley
> Fix For: 6.0
>
> Attachments: LUCENE_7056__split_spatial3d_package.patch, LUCENE_7056__split_spatial3d_package.patch
>
>
> The original description follows; it's greater in scope than the new title:
> ----
> This is a proposal for the "spatial3d" module to be purely about the shape/geometry implementations it has. In Lucene 5 that's actually all it has. In Lucene 6 at the moment its ~76 files have 2 classes that I think should go elsewhere: Geo3DPoint and PointInGeo3DShapeQuery. Specifically lucene-spatial-extras (which doesn't quite exist yet so lucene-spatial) would be a suitable place due to the dependency. _Eventually_ I see this module migrating elsewhere be it on its own or a part of something else more spatial-ish. Even if that never comes to pass, non-Lucene users who want to use this module for it's geometry annoyingly have to exclude the Lucene dependencies that are there because this module also contains these two classes.
> In a comment I'll suggest some specifics.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org