Allow catalina.base to be configured separately from catalina.home in the Tomcat managed adapters ------------------------------------------------------------------------------------------------- Key: ARQ-866 URL: https://issues.jboss.org/browse/ARQ-866 Project: Arquillian Issue Type: Enhancement Security Level: Public(Everyone can see) Components: Tomcat Containers Affects Versions: tomcat_1.0.0.CR3 Reporter: Dan Allen The Tomcat managed container adapter assumes that catalina.base is the same as catalina.home. {code} String absolutePath = new File(CATALINA_HOME).getAbsolutePath(); ... cmd.add("-Dcatalina.base=" + absolutePath); cmd.add("-Dcatalina.home=" + absolutePath); {code} However, this is not necessary true. For instance, when using Tomcat from Eclipse, the catalina.base (which includes the configuration files) is managed inside the Eclipse workspace. This allows the developer to modify Tomcat settings without affecting the system installation. The fix for this problem is to add a configuration property named "catalinaBase" and honor if it's set when building the startup script. This affects all the Tomcat managed containers (5, 6 and 7).