[
https://issues.jboss.org/browse/ARQ-574?page=com.atlassian.jira.plugin.sy...
]
Geoffrey De Smet commented on ARQ-574:
--------------------------------------
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.
Tomcat managed should not require an installed tomcat server
------------------------------------------------------------
Key: ARQ-574
URL:
https://issues.jboss.org/browse/ARQ-574
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Tomcat Containers
Reporter: Geoffrey De Smet
When starting up tomcat6-managed, the first SNAPSHOT, I get this:
{code}
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!
{code}
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira