Currently, downstream projects that want to integrate with different Hadoop-compatible file systems like WASB and S3A need to list dependencies on each one. This creates an ongoing maintenance burden for those projects, because they need to update their build whenever a new Hadoop-compatible file system is introduced. This issue proposes adding a new artifact that transitively includes all Hadoop-compatible file systems. Similar to hadoop-client, this new artifact will consist of just a pom.xml listing the individual dependencies. Downstream users can depend on this artifact to sweep in everything, and picking up a new file system in a future version will be just a matter of updating the Hadoop dependency version.