> On 16 Mar 2017, at 00:25, Junping Du <j...@hortonworks.com> wrote: > > bq. From my read of the poms, hadoop-client depends on hadoop-hdfs-client to > pull in HDFS-related code. It doesn't have its own dependency on hadoop-hdfs. > So I think this affects users of the hadoop-client artifact, which has > existed for a long time. > > I could miss that. Thanks for reminding! From my quick check: > https://mvnrepository.com/artifact/org.apache.hadoop/hadoop-client/2.7.3?, it > sounds like 669 artifacts from other projects were depending on it. > > > I think we should withdraw the current RC bits. Please stop the verification > & vote. > > I will kick off another RC immediately when HDFS-11431 get fixed.
is done. hadoop-hdfs without any server-side dependencies is now a hadoop-client dependency. Release notes: The hadoop-client POM now includes a leaner hdfs-client, stripping out all the transitive dependencies on JARs only needed for the Hadoop HDFS daemon itself. The specific jars now excluded are: leveldbjni-all, jetty-util, commons-daemon, xercesImpl, netty and servlet-api. This should make downstream projects dependent JARs smaller, and avoid version conflict problems with the specific JARs now excluded. Applications may encounter build problems if they did depend on these JARs, and which didn't explicitly include them. There are two fixes for this * explicitly include the JARs, stating which version of them you want. * add a dependency on hadoop-hdfs. For Hadoop 2.8+, this will add the missing dependencies. For builds against older versions of Hadoop, this will be harmless, as hadoop-hdfs and all its dependencies are already pulled in by the hadoop-client POM. --------------------------------------------------------------------- To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
