| git branch -m old_branch new_branch # Rename branch locally | |
| git push origin :old_branch # Delete the old branch | |
| git push --set-upstream origin new_branch # Push the new branch, set local branch to track the new remote |
To be used in conjunction of maven-publish to correctly generate an AAR Pomfile.
For some reason, I can't get maven-publish to generate a Pomfile when I'm exporting an Android library (AAR).
This plugin generates the Pomfile by looking at library's classpath and exclusions.
Usually while writing view binding code for android you need to declare your view components and then bind them to their respective views using findViewById which is a lot of hassle and can even reduce your performance if done in a wrong way. Typically is tedious and looks something like this.
class MainActivity extends Activity {
TextView title;
As we all know that Fabric is being migrated to Firebase and all Fabric features (Crashlytics, Beta, etc.) will have their equivalents in Firebase (Analytics, Distribution, etc.)
As a result we will need to migrate our current Fabric projects to Firebase in order to keep our analytic data and continue using other features like Beta distribution.
In this article I will try to simplify all the steps needed to migrate you project to Firebase, keep your analytics and configure automated releases using Fastlane and CircleCI.