This changes the dropbox-sdk-android modules from simply an included source set into a proper Android module.
Since the splitting of the Java and Android modules will be a large breaking change for many consumers if we continue using the dropbox-sdk-java artifact ID and they simply update the version, I propose that when we make this split (in 6.0.0) we use different artifact names. I'm thinking dropbox and dropbox-android, modeled after a similar approach for OkHTTP.
That will mean that instead of blindly updating the version from 5.x to 6.x and losing any of the Android goodness, consumers will have to actually update the artifact id to move, forcing them to choose the right one. That will come in a later PR.
rharter
commented
1 year ago
This changes the
dropbox-sdk-androidmodules from simply an included source set into a proper Android module.Since the splitting of the Java and Android modules will be a large breaking change for many consumers if we continue using the
dropbox-sdk-javaartifact ID and they simply update the version, I propose that when we make this split (in 6.0.0) we use different artifact names. I'm thinkingdropboxanddropbox-android, modeled after a similar approach for OkHTTP.That will mean that instead of blindly updating the version from 5.x to 6.x and losing any of the Android goodness, consumers will have to actually update the artifact id to move, forcing them to choose the right one. That will come in a later PR.