[
https://issues.apache.org/jira/browse/SOLR-15917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17475707#comment-17475707
]
David Smiley commented on SOLR-15917:
-------------------------------------
{quote}I agree that "module" makes more sense, as these are built with and
released along-side solr. So they are more a module of Solr, than a
package/plugin for it.
{quote}
I don't think that's a good reason because _where_ a package is doesn't mean
it's less/more of a package. 1st party vs 3rd party – still a package.
Any way, I suppose we could call the directory "modules" and rename it to
"packages" in 10.0 if they are converted by then. I'm trying to avoid a
multi-rename path into the future – shoot for the target now. But even more
I'd like to avoid having the CLI option be "modules" and then go away to become
"packages" later – lets just harmonize on the word "packages" and improve how
well they work internally as time goes on (initially simply JARs on the
classpath; eventually more). That's my 2 cents.
> Rename 'contrib' as 'module'
> ----------------------------
>
> Key: SOLR-15917
> URL: https://issues.apache.org/jira/browse/SOLR-15917
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Jan Høydahl
> Priority: Major
>
> Spinoff from SOLR-15914. The term 'module' communicates better that these are
> optional modules you can bring in if you want.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
