You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some hydra development relies on additional functionality in solr. In order to support that development, the projects have been pulling in the libraries and modifying the solrconfig.xml using an install generator. With this functionality being pushed down the stack to hydra works samvera/hydra-works#195, the option to use an install generator goes away.
Is adding contrib libraries and modifying the solrconfig something that the community is interested in providing as an option at the jettywrapper level? This could be related to #33, as optional arguments could be a method of implementing this.
The text was updated successfully, but these errors were encountered:
It just downloads the appropriate jars. There's are solr config files in Sufia as well that are copied over to the jetty directory as part of this process too. It would be nice if different config options could be exacted and shared across different projects. Maybe jettywrapper is the place to do that.
@jcoyne, Yes. A rake task to do install fulltext or something similar would be convenient. Since it's a jettywrapper related configuration change, the thought was that it should be an optional task that lives in jetty.
Some hydra development relies on additional functionality in solr. In order to support that development, the projects have been pulling in the libraries and modifying the solrconfig.xml using an install generator. With this functionality being pushed down the stack to hydra works samvera/hydra-works#195, the option to use an install generator goes away.
Is adding contrib libraries and modifying the solrconfig something that the community is interested in providing as an option at the jettywrapper level? This could be related to #33, as optional arguments could be a method of implementing this.
The text was updated successfully, but these errors were encountered: