[ 
https://issues.apache.org/jira/browse/HBASE-8950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Williams updated HBASE-8950:
----------------------------------

    Description: 
Currently, the HbaseTestingUtility is not importable in versions 0.94.x without 
Sonatype Aether dynamic classpath modification.  This is clunky and makes 
importing the utility opaque and unfriendly.  Please change this to make the 
HbaseTestingUtility visible and importable without special classpath 
modifications.

That is:
{code}
import org.apache.hadoop.hbase.HBaseTestingUtility;
{code}
should succeed after placing org.apache.hbase/hbase "0.94.X" and higher on the 
classpath.

  was:
Currently, the HbaseTestingUtility is not importable in versions 0.94.x without 
Sonatype Aether dynamic classpath modification.  This is clunky and makes 
importing the utility opaque and unfriendly.  Please change this to make the 
HbaseTestingUtility visible and importable without special classpath 
modifications.

That is:
{code}
import org.apache.hadoop.hbase.HBaseTestingUtility;
{code}

    
> Please Make HbaseTestingUtility Import without Dynamic Class Path Modification
> ------------------------------------------------------------------------------
>
>                 Key: HBASE-8950
>                 URL: https://issues.apache.org/jira/browse/HBASE-8950
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: David Williams
>
> Currently, the HbaseTestingUtility is not importable in versions 0.94.x 
> without Sonatype Aether dynamic classpath modification.  This is clunky and 
> makes importing the utility opaque and unfriendly.  Please change this to 
> make the HbaseTestingUtility visible and importable without special classpath 
> modifications.
> That is:
> {code}
> import org.apache.hadoop.hbase.HBaseTestingUtility;
> {code}
> should succeed after placing org.apache.hbase/hbase "0.94.X" and higher on 
> the classpath.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to