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
Buildout first initializes a recipe, then installs it and even later updates it.
As solr configuration depends on downloading solr
(done in a separate part with its own initialize, install and update),
checking for a file to exist on the other (download) part does not work on the initial phase,
but does on the install.
At the same time this recipe allows to override some templates,
so if the template is not overriden, an empty string is used (on the init phase).
Thus on the install phase, a correct path can be built.
ACTION: I don't see any 5.3.x branch, does anyone want to support this version any longer or everybody already moved to version 6? Given collective/collective.solr#66 and #43 I would rather say that 6 should be an alpha and newcomers to Solr with Plone should still stick to collective.recipe.solr 5.3.2 and Solr 4.10.x...
The text was updated successfully, but these errors were encountered:
Basically what derFreitag@138b3ad says:
Buildout first initializes a recipe, then installs it and even later updates it.
As solr configuration depends on downloading solr
(done in a separate part with its own initialize, install and update),
checking for a file to exist on the other (download) part does not work on the initial phase,
but does on the install.
At the same time this recipe allows to override some templates,
so if the template is not overriden, an empty string is used (on the init phase).
Thus on the install phase, a correct path can be built.
ACTION: I don't see any 5.3.x branch, does anyone want to support this version any longer or everybody already moved to version 6? Given collective/collective.solr#66 and #43 I would rather say that 6 should be an alpha and newcomers to Solr with Plone should still stick to collective.recipe.solr 5.3.2 and Solr 4.10.x...
The text was updated successfully, but these errors were encountered: