[
https://issues.apache.org/jira/browse/SOLR-13743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16935141#comment-16935141
]
Jan Høydahl commented on SOLR-13743:
------------------------------------
Plugin repository is well defined in PF4J, and I have 3-4 implementations ready:
* {{ApacheMirrorsUpdateRepository}}including ApacheMirrorsUpdateRepository,
GitHubUpdateRepository as well as default ones for local folder and, HTTP URL.
The repository manifest is a simple JSON file, listing all the plugins hosted,
with name, hash, signatures, version and a 'requires' expression that tells
what Solr versions this plugin version is compatible with. The repo class is
called:
!plugin-repo-format.png|width=800!
([https://www.slideshare.net/janhoy/solrs-missing-plugin-ecosystem/43])
> Add support for managing repository of packages
> -----------------------------------------------
>
> Key: SOLR-13743
> URL: https://issues.apache.org/jira/browse/SOLR-13743
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Ishan Chattopadhyaya
> Assignee: Ishan Chattopadhyaya
> Priority: Major
> Attachments: plugin-repo-format.png
>
>
> A user should be able to specify a repository of packages to install from. A
> repository will contain the following:
> # Manifest (containing package names, version, their jar names, public key,
> dependency information etc.).
> # Individual jar files
> # Signatures of the jar files
> In Solr, a package manager should be able to add a repository (one time) and
> subsequently, the packages should just be installed using the package name
> and version.
--
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
