the changes for the hdfs client classpath make instantiating HdfsConfiguration from the client impossible; it only lives server side. This breaks any app which creates one.
I know people will look at the @Private tag and say "don't do that then", but it's worth considering precisely why I, at least, do this: it's the only way to guarantee that the hdfs-default and hdfs-site resources get on the classpath, including all the security settings. It's precisely the use case which HdfsConfigurationLoader.init(); offers internally to the hdfs code.
What am I meant to do now?