[
https://issues.apache.org/jira/browse/LUCENE-10202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433521#comment-17433521
]
David Smiley commented on LUCENE-10202:
---------------------------------------
[~daddywri] when I was working on the PR to name the "feature variant"
implemented by the spatial3d module, I was contemplating what to name it. I
should probably pick the obvious name – "spatial3d" after the dependency it
brings in. But its name had me thinking (and we've been over this in the past)
about how difficult it is to name that module. "3d" gives people the wrong
impression. When I tell people about that module, I say it has "surface of a
sphere geometry" (and yes it does ellepsoid, I know). Thus perhaps
"spatial-spherical" might have been a better name?
> Expose dependencies using Gradle Feature Variants
> -------------------------------------------------
>
> Key: LUCENE-10202
> URL: https://issues.apache.org/jira/browse/LUCENE-10202
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/spatial-extras
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Minor
>
> The spatial-extras module has several dependencies. However some of them
> like spatial3d (aka Geo3d) are only needed for certain features. Likewise,
> JTS could be exposed here as well, and should be opt-in. In Maven, these
> should be "optional". Gradle has a cool alternative for Gradle consumers to
> select named "feature variants" this module could expose so that it doesn't
> have to pick the right dependency versions.
> https://docs.gradle.org/current/userguide/feature_variants.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
