In January 2017, the usage of build tools in Github's top 1000 Java repositories is as follows:
| Tool Name | Reference Count |
|---|---|
| Gradle | 627 |
| Maven | 264 |
| Ant | 52 |
| Npm | 4 |
| Bazel | 3 |
| Make | 1 |
And the trending over the past 8 years is:
- Clone top 1000 Java repositories to local disk
- Analyze the repositories by identity files:
| Tool Name | Identity Files |
|---|---|
| Gradle | build.gradle |
| Maven | pom.xml |
| Ant | build.xml |
| Npm | package.json |
| Bazel | BUILD |
| Make | Makefile/makefile |
- Make sure Git/Groovy 2.4+/JDK 1.7+ are installed.
- Run
groovy GithubTopRankCrawler.groovy -l java -d <path to store the 1000 repos>to clone all repositories locally. - Run
groovy JavaBuildToolScanner.groovy -d <path to store the 1000 repos>to analyze these repos.
There are various package management tools for golang as listed here. But which one is the most popular?
The usage of package manage tools in Github's top 1000 Go repositories is as follows:
| Tool Name | Url | Reference Count (Feb 2017) | Reference Count (Nov 2017) |
|---|---|---|---|
| Makefile | Makefile | 199 | 181 |
| dep | dep | N/A | 94 |
| godep | godep | 119 | 90 |
| govendor | govendor | 65 | 84 |
| glide | glide | 64 | 77 |
| gvt | gvt | 25 | 16 |
| trash | trash | 7 | 13 |
| submodule | submodule | 8 | 6 |
| gpm/johnny-deps | gpm johnny-deps | 7 | 6 |
| glock | glock | 5 | 4 |
| gom | gom | 4 | 2 |
| gopack | gopack | 3 | 2 |
| gopm | gopm | 3 | 1 |
| goop | goop | 1 | 1 |
| gvend | gvend | 2 | 0 |
dep had a first release in May 2017, did not exist for first stats.
Technically, make is not a package management tool, here it is just for comparison.
Submodule refers to a set of tools which use git submodule to manage dependencies such as manul and Vendetta and so on.
- Clone top 1000 Go repositories to local disk
- Analyze the repositories by identity files:
| Tool Name | Identity Files |
|---|---|
| godep | Godeps/Godeps.json |
| govendor | vendor/vendor.json |
| gopm | .gopmfile |
| gvt | vendor/manifest |
| gvend | vendor.yml |
| glide | glide.yaml or glide.lock |
| trash | vendor.conf |
| gom | Gomfile |
| bunch | bunchfile |
| goop | Goopfile |
| goat | .go.yaml |
| glock | GLOCKFILE |
| gobs | goproject.json |
| gopack | gopack.config |
| nut | Nut.toml |
| gpm/johnny-deps | Godeps |
| Makefile | makefile or Makefile |
| submodule | .gitmodules |
- Make sure Git/Groovy 2.4+/JDK 1.7+ are installed.
- Run
groovy GithubTopRankCrawler.groovy -l go -d <path to store the 1000 repos>to clone all repositories locally. You can use-sto do the shallow clone and decrease disk usage. - Run
groovy GoBuildToolScanner.groovy <path to store the 1000 repos>to analyze these repos.