You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mrunit.apache.org by "Jim Donofrio (Updated) (JIRA)" <ji...@apache.org> on 2012/04/20 07:09:37 UTC

[jira] [Updated] (MRUNIT-104) move non user classes into internal package

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

Jim Donofrio updated MRUNIT-104:
--------------------------------

    Description: 
Users should never call the below classes, to avoid confusion and clean up the javadoc they should be moved to the internal package. This also gives us more flexiblity to make changes in the future.

Serialization to internal.io
mock package to internal.mapred
mapreduce.mock package to internal.mapreduce
CounterWrapper to internal.counters

  was:
Users should never call the below classes, to avoid confusion and clean up the javadoc they should be moved to the internal package. This also gives us more flexiblity to make changes in the future.

Serialization to internal.util
mock package to internal.mapred.mock
mapreduce.mock package to internal.mapreduce.mock
CounterWrapper to internal.counters

    
> move non user classes into internal package
> -------------------------------------------
>
>                 Key: MRUNIT-104
>                 URL: https://issues.apache.org/jira/browse/MRUNIT-104
>             Project: MRUnit
>          Issue Type: Task
>    Affects Versions: 0.9.0
>            Reporter: Jim Donofrio
>            Assignee: Jim Donofrio
>             Fix For: 1.0.0
>
>
> Users should never call the below classes, to avoid confusion and clean up the javadoc they should be moved to the internal package. This also gives us more flexiblity to make changes in the future.
> Serialization to internal.io
> mock package to internal.mapred
> mapreduce.mock package to internal.mapreduce
> CounterWrapper to internal.counters

--
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