You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you clone the repo, you can change the value of project.ext.supportLibraryVersion in build.gradle to the new version of the support lib whenever you want. On major version upgrades (like from 25 to 26) you will have to change both buildToolsVersion and sdkVersion to an appropriate value.
I usually try to update the maven repo the day the new support lib is available (sometimes even faster 😄), so the current update path shouldn't be a problem really.
@Gericop If I clone the project and change it myself, that's mean I will include the project as library source project. I can no longer include it by using build.gradle right?
Thank you very much, for keep updating this library, to keep it in sync with Google new support library.
However, time-to-time, Google will keep releasing new support library in fast pace.
Instead of waiting the owner of Android-Support-Preference-V7-Fix, to update Android-Support-Preference-V7-Fix .
Is there any way we can DIY ourselves, for us to make this library in sysnc with Google new support library?
I saw whenever there is new release, the owner makes the following changes 955a03b
Is there any way we can do this by our own, and compile against our own project?
The text was updated successfully, but these errors were encountered: