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

Chia-Ping Tsai commented on HBASE-14848:
----------------------------------------

hbase-procedure's dependencies has hbase-client-tests so it can use the 
log4j.properties of hbase-common.
{code:java}
<dependency>
  <groupId>org.apache.hbase</groupId>
  <artifactId>hbase-common</artifactId>
  <version>${project.version}</version>
  <classifier>tests</classifier>
</dependency>{code}
HBASE-14085 overwrite the folder of test resources for hbase-common so it won't 
copy the resources/log4j.properties to target/test-classes anymore. 
hbase-endpoint, by contrast, it need not have the log4j.properties as it 
reference the hbase-server-tests.
{code:java}
<testResources>
  <testResource>
    <directory>src/test/resources/META-INF/</directory>
    <targetPath>META-INF/</targetPath>
    <includes>
      <include>NOTICE</include>
    </includes>
    <filtering>true</filtering>
  </testResource>
</testResources>{code}
HBASE-19877 will fix the log4j.properties for hbase-common/hbase-zookeeper. 
However, It is worthwhile to reorganize our log property since most (all?) 
properties are same...

 

> some hbase-* module don't have test/resources/log4j and test logs are empty
> ---------------------------------------------------------------------------
>
>                 Key: HBASE-14848
>                 URL: https://issues.apache.org/jira/browse/HBASE-14848
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 2.0.0, 1.2.0, 1.1.2, 1.3.0
>            Reporter: Matteo Bertozzi
>            Priority: Major
>         Attachments: hbase-procedure-resources.patch
>
>
> some of the hbase sub modules (e.g. hbase-procedure, hbase-prefix-tree, ...) 
> don't have the test/resources/log4j.properties file which result in unit 
> tests not printing any information.
> adding the log4j seems to work, but in the past the debug output was visibile 
> even without the file.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to