[jira] [Commented] (HBASE-16298) ESAPI.properties missing in hbase-server.jar

["stack (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-16298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398768#comment-15398768 ] 

stack commented on HBASE-16298:
-------------------------------

Makes sense [~sveyrie]. Any chance of a patch sir?

> ESAPI.properties missing in hbase-server.jar
> --------------------------------------------
>
>                 Key: HBASE-16298
>                 URL: https://issues.apache.org/jira/browse/HBASE-16298
>             Project: HBase
>          Issue Type: Bug
>          Components:  Interface
>    Affects Versions: 1.1.5, 1.2.2
>         Environment: Debian 8.2
> Linux 3.16.0-4-amd64
> OpenJDK 8u91-b14-3ubuntu1~16.04.1
>            Reporter: Sylvain Veyrié
>
> For policy/compliance reasons, we removed the tests jars from lib/ directory on HBase Master. Everything was working fine from 1.0 to 1.1.3.
> When I upgraded from 1.1.3 to 1.1.5, the /master-status page started to return an error 500: {{java.lang.IllegalArgumentException: Failed to load ESAPI.properties as a classloader resource.}}
> After some search, I found out that ESAPI has been added following HBASE-15122 which also added the ESAPI.properties files into src/main/resources.
> However, it seems an exclusion has been put on packaging: the file is absent from hbase-server-1.1.5.jar, but present in hbase-server-1.1.5-tests.jar, which is in the lib/ directory in the tar.gz distribution.
> Our workaround is to deploy back hbase-server-1.1.5-tests.jar in lib/. However, it does not seem right to require tests jar to have HBase master propertly work.
> Even if it is the current HBase policy to keep those jars, I think the hbase-server.jar should contain ESAPI.properties.
> The same thing applies for 1.2 branch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)