We want to package our app as a single, versioned, easy-to-deploy
artifact for our customers.
However, we use solr for search in our app, and we’re wondering how
this will work, since solr is packaged in its own war file, and needs
an app-specific schema config file (which changes as the app evolves).
How would you approach this? Here’s some options, advice on the best
one or others is welcome:
Deploy separate war files, one for the app and one for solr? In
this case, where does the schema file live? We could rebuild the Solr
war with our schema file on every deploy, but it seems wrong to
repackage solr for that purpose. Or we could have the schema file be
a flat file on the system. Either way, the customer will have to
manage multiple artifacts on deploys.
Package the app as an EAR? Packaging multiple wars and configs is
the purpose of EAR files, but I see very little mention of EARs +
Jruby on the web.
To unsubscribe from this list, please visit: