[
https://issues.apache.org/jira/browse/HADOOP-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665788#action_12665788
]
Steve Loughran commented on HADOOP-5023:
----------------------------------------
Presumably the problem here is that a tomcat installation is required on the
local machine? And then its install directory set in the env variable or adding
env.HDFSPROXY_CONF_DIR to the build directories?
# we may be able to have Ivy pull down a copy of tomcat, though as it would
require a full unzip and introduces some security issues, I'm not enthusiastic
about this. I see that <cargo> does contain a URL to a tomcat version; without
at least MD5 checking that's something to worry about.
# all the cactus tests should be skipped if the env variable is not set.
<fileset> work can do that, relatively easily.
# Another option is functional testing with HtmlUnit. This can be used for
testing all of the web sites, so is going to be need at some point in the
future anyway. Instead of running junit tests remotely with via cactus, hit
some test pages from the outside and see they return the expected response
> Add Tomcat support to hdfsproxy
> -------------------------------
>
> Key: HADOOP-5023
> URL: https://issues.apache.org/jira/browse/HADOOP-5023
> Project: Hadoop Core
> Issue Type: Improvement
> Components: contrib/hdfsproxy
> Reporter: Kan Zhang
> Assignee: zhiyong zhang
> Attachments: HADOOP-5023.patch
>
>
> We plan to add Tomcat support to hdfsproxy since Tomcat has good production
> support at Yahoo.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
