# drone **Repository Path**: ouyangpengdev/drone ## Basic Information - **Project Name**: drone - **Description**: :cake: The missing library manager for Android Developers - **Primary Language**: JavaScript - **License**: MIT - **Default Branch**: master - **Homepage**: None - **GVP Project**: No ## Statistics - **Stars**: 0 - **Forks**: 0 - **Created**: 2021-03-23 - **Last Updated**: 2021-03-23 ## Categories & Tags **Categories**: Uncategorized **Tags**: None ## README

Drone

The missing library manager for Android Developers

Build Status npm npm License

### Summary - :zap: Blazing fast way to add libraries - :tada: No need to search the web for `that` library - :rocket: Intuitive, easy-to-learn tool - :gem: Add multiple dependencies with a one liner - :v: Automated dependency and package management - :hammer: Automatic import custom urls (e.g. jitpack) ### What is it? As an android developer I was jealous of the node.js community for their fast and reliable dependency managers, it's so easy to write `yarn add ` and a library is imported into the project... So I made `drone` for android! If you think about it there are like 50 libraries that are used in 95% of the apps (retrofit, rxjava, gson, picasso, roboletric, recyclerview-v7, etc.) I made this because every time I want to add (lets say) butterknife I need to 1. google butterknife 2. go to the readme 3. find the lines to copy 4. notice that butterknife has 2 dependencies 5. copy and paste in my gradle file 6. OPTIONAL if it was not in jcenter, go to the main build gradle and put the custom URL OR... ```sh drone add jakewharton/butterknife ``` and everything will be done for you automatically ## Install ```sh npm install -g drone ``` ## Usage Simple usage: > `drone` add `creator/library` `module`

``` Usage $ drone $ drone install # Downloads the packages $ drone test # Tests the library by fetching its version $ drone add # Adds a dependency to a module $ drone remove # Removes the dependency from a module $ drone info # Retrieves the info for this package $ drone update # Get the latest packages $ drone list # List all of the packages $ drone stats # Get some stats regarding the hive $ drone hive # Opens the hive url $ drone open # Opens the library's homepage $ drone new # Creates a new one if it's not in the server yet $ drone search # Searches for the 'library' in the hive Examples $ drone install # Downloads the packages $ drone info square/picasso # Shows the info for square/picasso $ drone add square/retrofit app # Adds retrofit to the 'app' module $ drone rm square/retrofit app # removes retrofit from the 'app' module $ drone open google/gson # Opens GSONs homepage $ drone new # takes you through the creation wizard $ drone search rxjava # Searches the hive for 'rxjava' $ drone test square/picasso # Tests the library by fetching its version ``` # Where are the libraries? Instead of maintaining a server with all the possible libraries I'm going with a [brew](https://brew.sh/) approach, the community will `create` a library `once` and it will be available to everyone else forever in the [hive](https://github.com/cesarferreira/drone-hive)! > $ drone new follow the wizard to generate the `.json` file then open the pull request in the [hive](https://github.com/cesarferreira/drone-hive) with this format: > **hive/``.json**

If you look closely, when you type `square/retrofit`, `drone` will autofill everything for you, and even if it takes a few hours for the pull request to be accepted you'll be able to do `drone add square/retrofit` because the `drone new` task will add it to your personal server/folder. ## Created by [Cesar Ferreira](https://cesarferreira.com) ## License MIT © [Cesar Ferreira](http://cesarferreira.com) ## Logo by Freepik from www.flaticon.com is licensed by CC 3.0 BY