[Solr Wiki] Update of "WhyNoWar" by ShawnHeisey

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.

The "WhyNoWar" page has been changed by ShawnHeisey:
https://wiki.apache.org/solr/WhyNoWar?action=diff&rev1=4&rev2=5

Comment:
Beefed up the section about deploying in another container.

  
  The deployment options available in Solr 4.x encouraged people to deploy Solr in untested and unsupported ways, or to deploy Solr along with other web applications in the same container.  Solr may not perform very well when the container is shared with other applications.  Sometimes even sharing the ''machine'' with other applications can be problematic.
  
- == Can I still deploy in another container? ==
+ == Can I still deploy Solr 5.x in another container? ==
  
  For the moment, yes.  There is still a solr.war file in the download, found in the server/webapps directory.  If you take that solr.war file, the logging jars in server/lib/ext, and the log4j.properties in server/resources, then you can deploy in a third-party servlet container just like you could with Solr 4.x.
  
+ Note that if you choose to do this kind of deployment, you are on your own.  The project cannot support every container out there.  Solr already has problems deploying in some containers, even with older releases that DID have the .war file in the dist directory.  There is a guava dependency problem that prevents Solr from running in GlassFish 4.x, documented in [[https://issues.apache.org/jira/browse/SOLR-5109|SOLR-5109]].  This bug has been closed with a status of "Won't Fix" because we no longer officially support deploying in a user-provided container.
+ 
  Eventually, most likely in a later 5.x version, Solr will become a completely standalone application.  When that happens, there will be no guarantee that users can still compile Solr as a war file and deploy in a third-party container.  Hopefully that will be an option for all of 5.x, but that option is currently expected to disappear with 6.0.