TACHYON-198 Move UserConf usage to use TachyonConf

This PR consist next steps to integrate new configuration work:
-) Remove usage of UserConf
-) Push TachyonConf to Tachyon Hadoop's file system (aka TFS class).
-) Remove UserConf.java from repo.
My point is it shouldn't. Extending classes should get their values from
methods rather than field access. This is helpful for testing, helpful for
maintenance (someone removed final, still protected) and the JVM will
remove it at run time, so the method had zero cost
On Dec 13, 2014 10:41 AM, "Henry Saputra" <notifications@github.com> wrote:

> In core/src/main/java/tachyon/client/AbstractTachyonFS.java
> <https://github.com/amplab/tachyon/pull/564#discussion-diff-21790256>:
>
> >
> >  /**
> >   * Abstract implementation of {@link tachyon.client.TachyonFSCore} APIs.
> >   */
> >  abstract class AbstractTachyonFS implements TachyonFSCore {
> > +  protected final TachyonConf mTachyonConf;
>
> This member variable can and will be accessed the class extending this
> abstract class that is why protected scope is used.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/amplab/tachyon/pull/564/files#r21790256>.
>