On 2/24/2015 1:16 AM, Thomas Scheffler wrote: > I noticed that not only SOLR does not deliver a WAR file anymore but > also advices not to try to provide a custom WAR file that can be > deployed anymore as future version may depend on custom jetty features. > > Until 4.10. we were able to provide a WAR file with all the plug-ins we > need for easier installs. The same WAR file was used together with an > web application WAR running integration tests and to check if all > application details still work. We used the cargo-mave2-plugin and > different servlet container for testing. I think this is quiet common > thing to do with continuous integration. > > Now I wonder if anyone has a similar setup and with integration tests > running against SOLR 5. > > - No artifacts can be used, so no local repository cache is present > - How to deploy your schema.xml, stopwords, solr plug-ins etc. for > testing in an isolated environment > - What does a maven boilerplate code look like?
I don't know anything at all about Maven. For now, Solr 5.x *is* still deployed as a .war file, which you can find in the download in the server/webapps directory ... but the plan is to eventually create a standalone application for Solr instead of running Jetty. Those plans are expected to happen during the 5.x timeframe, which is why the documentation advises against relying on the .war file. It eventually *will* disappear, and it's important to prepare the userbase for that well in advance of the actual implementation. I have a custom install based on the jetty included with Solr 4.x. When I upgrade, I will continue to use the war as long as it is available, and when the standalone app appears, I will either reconfigure my init script or see about switching over to the script included with the 5.x download. Thanks, Shawn
