For searchbots, the error says
The Apache Tomcat installation at this directory is version 8.5.3. A Tomcat 8.0 installation is expected. This error even occurs in the current Eclipse Neon release. Perhaps they'll fix it in Neon SR1 by adding a new Tomcat v8.5 Server plugin. But for now and for older versions a workaround is needed.
The Eclipse built-in Tomcat server plugin basically detects the server version based on
server.info property of
org/apache/catalina/util/ServerInfo.properties file of Tomcat's
/lib/catalina.jar file which looks like below in case of Tomcat 8.5.3:
server.info=Apache Tomcat/8.5.3 server.number=188.8.131.52 server.built=Jun 9 2016 11:16:29 UTC
All we need to do is to edit the version in
server.info property to start with
8.0. Any ZIP or JAR aware tool should do it to edit it on the fly. I'm myself using WinRAR for the job.
server.info=Apache Tomcat/184.108.40.206.3 server.number=220.127.116.11 server.built=Jun 9 2016 11:16:29 UTC
Finally, it works.
INFO: Starting Servlet Engine: Apache Tomcat/18.104.22.168.3
The same procedure applies to TomEE 7.x which is based on Tomcat 8.5.x.
The difference between Tomcat 8.0 and 8.5 is the integration of Jaspic which is the first step towards standardizing Java EE authentication as part of JSR375. You probably already know that the ways to configure Java EE container managed authentication are totally scattered across different servers, making third party libraries such as Shiro and Spring Security more attractive. Each server needed its own way of configuring "realms" or "identity stores" to manage the database of users, passwords and roles. This will with JSR375 be unified using annotations and CDI provided via standard
javax.security.* API. See also a.o. the question Java EE authentication: how to capture login event?