tomcat-vault RPM structure needs attention

The tomcat-vault RPM structure is similar to the EAP RPM structure, however it is an unrelated library so that is a bit confusing. The tomcat-vault RPM installs into /usr/share/java/modules/system/layers/base/tomcat-vault, but EAP 6 installs modules into /usr/share/jbossas/modules and EAP 7 uses the RHSCL structure, /opt/rh/eap7/root/usr/share/wildfly/modules. Additionally, EAP doesn't even use the tomcat-vault JAR, it includes the required classes for vault in the jboss-as-security*.jar. None of these paths match and none of them have overlapping classpaths. The package is also missing a dependency on a tomcat package.

With all that said, here are the questions I'd like to answer with this issue:

Should a user be able install tomcat-vault without tomcat? Or will we treat it like a separate tool instead of just a runtime dependency?
Should we amend the tomcat-vault package so that it installs into the tomcat structure rather than it's own? Or did we do this because the script can be
reused for tomcat without modification?