Is there any good reason for keeping solr_home within the webapp? It should work, but I would not recommend it. Have you configured solr_home somewhere? One way in Tomcat is to do something like this:
-- <Context...> <Environment name="solr/home" type="java.lang.String" value="[your_solr_home]" override="true"/> </Context> -- in either: $tomcat_home/conf/Catalina/localhost/solr.xml or in $tomcat_home/conf/server xml. A better solution would probably be a maven project, but with two modules. This way you could build the modules together or individually. Then you can make adjustments to the config and reload core's at will, a feature you would lose with keeping solr_home within the webapp. Regards, Ingar On Wed, Mar 28, 2012 at 1:39 PM, Aleksander Akerø <solraleksan...@gmail.com> wrote: > Hi > > > > My company has just decided to use maven to build new projects, which then > includes building solr with maven too. > > But then it has been decided that solr_home also should be installed within > the webapp someplace. But now I have got the problem that solr can’t find > the config files and so on. I have come across some posts here and there > which says that solr_home should not be placed within the webapp. > > Is that correct? If so, what are the reasons for it, and should it not work > at all? > > > > Aleksander Akerø >
