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 <do...@gmail.com> on 2012/04/20 05:32:53 UTC
[DISCUSS] move classes into internal package?
I would like to move some of the classes that users dont need to know
about into the internal package so that they will see no javadoc on them
and be encouraged not to use them. What are the thoughts on moving the
following:
Serialization to internal.util
mock package to internal.mapred.mock
mapreduce.mock package to internal.mapreduce.mock
CounterWrapper to internal.counters
I understand that moving classes around is usually bad but no users
should have called these classes directly anyway.
Re: [DISCUSS] move classes into internal package?
Posted by Jarek Jarcec Cecho <ja...@apache.org>.
I also do not mind moving those classes into internal (private) package.
Jarcec
On Thu, Apr 19, 2012 at 11:18:04PM -0500, Brock Noland wrote:
> I am fine with this as those classes shouldn't be used by users.
>
> On Thu, Apr 19, 2012 at 10:32 PM, Jim Donofrio <do...@gmail.com> wrote:
> > I would like to move some of the classes that users dont need to know about
> > into the internal package so that they will see no javadoc on them and be
> > encouraged not to use them. What are the thoughts on moving the following:
> >
> > Serialization to internal.util
> > mock package to internal.mapred.mock
> > mapreduce.mock package to internal.mapreduce.mock
> > CounterWrapper to internal.counters
> >
> > I understand that moving classes around is usually bad but no users should
> > have called these classes directly anyway.
>
>
>
> --
> Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/
Re: [DISCUSS] move classes into internal package?
Posted by Brock Noland <br...@cloudera.com>.
I am fine with this as those classes shouldn't be used by users.
On Thu, Apr 19, 2012 at 10:32 PM, Jim Donofrio <do...@gmail.com> wrote:
> I would like to move some of the classes that users dont need to know about
> into the internal package so that they will see no javadoc on them and be
> encouraged not to use them. What are the thoughts on moving the following:
>
> Serialization to internal.util
> mock package to internal.mapred.mock
> mapreduce.mock package to internal.mapreduce.mock
> CounterWrapper to internal.counters
>
> I understand that moving classes around is usually bad but no users should
> have called these classes directly anyway.
--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/