accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Billie Rinaldi (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-175) Mock Accumulo yields classpath errors
Date Tue, 22 Nov 2011 22:22:40 GMT

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

Billie Rinaldi updated ACCUMULO-175:
------------------------------------

    Description: Mock Accumulo is used for our junit tests. There are users out there who
would like to use it for testing applications built on top of Accumulo. This causes errors
due to the way we set up classloading, etc. since we don't do any of the fancy behind-the-scenes
magic for classpaths when mocking. We should tweak either the way the classloader works, or
the way iteratorutils works, or how MockAccumulo is stood up to ensure whatever classloader
is used is working transparently to the user.  (was: Mock Accumulo is used for our junit tests.
There are users out there who would like to use it for testing applications built on top of
cloudbase. This causes errors due to the way we set up classloading, etc. since we don't do
any of the fancy behind-the-scenes magic for classpaths when mocking. We should tweak either
the way the classloader works, or the way iteratorutils works, or how MockAccumulo is stood
up to ensure whatever classloader is used is working transparantly to the user,)
    
> Mock Accumulo yields classpath errors
> -------------------------------------
>
>                 Key: ACCUMULO-175
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-175
>             Project: Accumulo
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 1.3.5
>            Reporter: John Vines
>            Assignee: John Vines
>              Labels: classloader
>             Fix For: 1.3.6
>
>
> Mock Accumulo is used for our junit tests. There are users out there who would like to
use it for testing applications built on top of Accumulo. This causes errors due to the way
we set up classloading, etc. since we don't do any of the fancy behind-the-scenes magic for
classpaths when mocking. We should tweak either the way the classloader works, or the way
iteratorutils works, or how MockAccumulo is stood up to ensure whatever classloader is used
is working transparently to the user.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message