Currently all the extensions are in one library. This library has a dependency to appcompat. So if the library is used by a project that doesn't use appcompat, it will be automatically added (unless it's explicitly excluded).
It would be good to divide the library to a set of libraries that contains extensions for each module, e.g.
android classes
support v4
appcompat
Additionally, a no-code module could be created, which can contain dependencies to all the separate modules. It's the same approach that is currently used e.g. by Google Play Services.
Currently all the extensions are in one library. This library has a dependency to appcompat. So if the library is used by a project that doesn't use appcompat, it will be automatically added (unless it's explicitly excluded). It would be good to divide the library to a set of libraries that contains extensions for each module, e.g.
Additionally, a no-code module could be created, which can contain dependencies to all the separate modules. It's the same approach that is currently used e.g. by Google Play Services.