I'm using Fabric for the Twitter SDK on Android, and it is just the same there. No, I don't want an IDE plugin that rewrites (read: messes up) my config files

I'm using Fabric for the Twitter SDK on Android, and it is just the same there. No, I don't want an IDE plugin that rewrites (read: messes up) my config files to "help" me install things. All I need is a website to generate API keys and a package URL to add to the dependencies file. The IDE plugin must have taken quite a bit of effort as well - not sure why and how someone at Twitter considered it to be a good idea. Perhaps a misguided attempt at "capturing developer mindshare" or the arrogant assumption that Twitter/Fabric SDKs are important parts of people's apps?