hadoop-common still declares a dependency on jets3t, which allows downstream projects to pick it up. But as they can't get s3n to work without the hadoop-aws JAR, it's hard to see how much use this is.
I propose: moving it to a dependency of hadoop-aws JAR alone.
Marking as incompatible as it will be in the specific situation
- downstream maven build doesn't pull in hadoop-aws
- command line doesnt have hadoop-aws JAR dependencies on CP and still wants to use jets3t. Hard to imagine how this arises.