1. The WARN messages "JBAS015960: Class Path entry" comes from including

   org.jboss.spec.javax.servlet, org.jboss.spec.javax.servlet.jsp, org.jboss.spec.javax.servlet.jstl

   that were added to make this error go away:

   java.lang.NoClassDefFoundError: javax/servlet/http/HttpServletRequest

   This has to do with the java/jdt difference. When these jars are added the resulting WARN messages dealing with the xalan.jar and serializer.jar occurs. According to this Solution it has to do with the offending jar having a reference to the "class-path" in it's MANIFEST.mf file. The solution only suggests filtering the log so that you don't see this warning.

2. The "JBAS018568: ... unsupported module" referring to the h2 database is there because EAP is telling us that we are using a private module and that may cause problems in the future if things change. The h2 database needs to be specifically included so that it may be used by the unit tests. If you were to remove all references to h2 from the pom.xml and jboss-deployment-structure.xml and then run the maven build with

   mvn clean package -DskipTests=true jboss-as:deploy

   everything will work fine. However if you remove h2 references but don't skip the test phase then there will be errors in the build.

3. The "JBAS018567: ... using a private module" is the same as the h2 database problem. These libraries are included only for testing.
4. "JBAS011006: Not installing optional component" is telling us that the class listed does not have a no-arg constructor in it. This must be fixed at the source.

I recommend that all of these WARN messages be ignored and this issue be REJECTED.