On Wed, Jul 29, 2009 at 2:42 PM, Chantal Ackermann < chantal.ackerm...@btelligent.de> wrote:
> Hi all, > > the environment variable (env-entry) in web.xml to configure the solr/home > is relative to the web server's working directory. I find this unusual as > all the servlet paths are relative to the web applications directory (webapp > context, that is). So, I specified solr/home relative to the web app dir, as > well, at first. > > I think it makes deployment in an unknown environment, or in different > environments using a simple war more complex than it needed to be. If a > webapp relative path inside the war file could be used, the configuration of > solr (and cores) could be included in the war file completely with no > outside dependency - except, of course, of the data directory if that is to > go some place else. > (In my case, I want to deliver the solr web application including a custom > entity processor, so that is why I want to include the solr war as part of > my release cycle. It is easier to deliver that to the system administration > than to provide them with partial packages they have to install into an > already installed war, imho.) > You don't need to create a custom war for that. You can package the EntityProcessor into a separate jar and add it to solr_home/lib directory. -- Regards, Shalin Shekhar Mangar.
