Details
-
Type:
Enhancement
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution:
Won't Fix
-
Affects Version/s: None
-
Fix Version/s: tomcat_1.0.0.CR7
-
Component/s: Tomcat Containers
-
Labels:None
Description
When starting up tomcat6-managed, the first SNAPSHOT, I get this:
Either CATALINA_HOME environment variable or catalinaHome property in Arquillian configuration must be set and point to a valid directory! null is not valid directory!
|
There are 2 problems with this:
- it's a maintenance hurdle, especially on hudson build slaves
- the build is not reproducible: the test results depends on the tomcat server version you've installed on your machine.
Solution:
Set the tomcat zip as a dependency (so it's in ~/.m2/repository) and unzip it to target and use that server installation.
Gliffy Diagrams
Issue Links
- is blocked by
-
ARQ-576
The build script bits that downloads and configures 1 or more managed containers should be extracted to a maven plugin, so we don't need to copy paste that logic
-
- Coding In Progress
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
Nope, doesn't look like they deploy a zip dist to the maven repo (note that glassfish does that):
http://search.maven.org/#search|ga|1|g%3A%22org.apache.tomcat%22
Maybe we can deploy one under org.jboss.arquillian.container ? We'd be able to throw out the examples overhead and credentials problems.
Still, it would be nice to have arquillian handle it instead of our builds:
- if I copy paste it that build script and you improve that build script, I 'll still be using the old version.
Geoffrey De Smet
added a comment - Nope, doesn't look like they deploy a zip dist to the maven repo (note that glassfish does that):
http://search.maven.org/#search |ga|1|g%3A%22org.apache.tomcat%22
Maybe we can deploy one under org.jboss.arquillian.container ? We'd be able to throw out the examples overhead and credentials problems.
Still, it would be nice to have arquillian handle it instead of our builds:
if I copy paste it that build script and you improve that build script, I 'll still be using the old version.
If we want this as a feature of Arquillian, it should be dealt with on a different level, not by the individual container adaptors. A Container adaptors responsibilities are start/stop/deploy/undeploy.
Aslak Knutsen
added a comment - If we want this as a feature of Arquillian, it should be dealt with on a different level, not by the individual container adaptors. A Container adaptors responsibilities are start/stop/deploy/undeploy. 
this is not up to the Container impl to handle, see https://github.com/arquillian/arquillian-container-tomcat/blob/master/tomcat-managed-6/pom.xml#L92 for example of how to download and extract a Tomcat instance.
(i don't think tomcat has a zip dist in a Maven repo)