secrets-gradle-plugin
dependency-analysis-gradle-plugin
| secrets-gradle-plugin | dependency-analysis-gradle-plugin | |
|---|---|---|
| 3 | 9 | |
| 1,033 | 1,617 | |
| 1.7% | - | |
| 4.7 | 9.6 | |
| 8 days ago | 5 days ago | |
| Kotlin | Kotlin | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
secrets-gradle-plugin
-
Simple Google Map App - Jetpack Compose
Secrets Gradle Plugin is basically a library to help you hide your API key without committing it to the version control system.
-
Keep API Key Outside of Gradle and Git
I use this for storing my keys. (Recommended by Google also) https://github.com/google/secrets-gradle-plugin
- Where do you put your secrets (api keys)?
dependency-analysis-gradle-plugin
- Recommended dependency analyzer plugin
-
References for Library & SDK Design?
And perhaps https://github.com/autonomousapps/dependency-analysis-android-gradle-plugin
-
android devs in multi-modular projects be like
I'd love to hear more about the complexity of configuring multi-module builds. Dependency management is an obvious point here and there are plugin that can help here (like https://github.com/autonomousapps/dependency-analysis-android-gradle-plugin for instance), but I'd be happy to hear more pain points.
-
Gradle all the way down: Testing your Gradle plugin with Gradle TestKit
Added a new test suite, named "functionalTest", and configured it to use the Spock test framework, along with three dependencies: Truth, TestKit-Truth, and the project itself. This reveals the interesting point that, by default, new test suites don't have the project under test on the classpath, which enables true black box testing if you're into that kind of thing.
-
Learning in public: Lessons from open source
A little more than two years ago, in October 2019, I began work on my first significant open source project, the Dependency Analysis Gradle Plugin. I had just left a job where I had done relatively little coding, was taking a month off, and wanted to get back into a building mode and learn some new things. I decided to explore the domain of unused-dependency detection. The nearest competitor I was aware of was the Gradle Lint Plugin from the Netflix Nebula collection. However, as that plugin has never supported Android projects, that meant I had an exploitable niche—if only I could exploit it.
-
Herding Elephants – Wrangling a 3,500-module Gradle project
Tony actually wrote a plugin that does just this! Check it out!
-
Reducing my Gradle plugin's impact on configuration time: A journey
(The commit is available here.)
What are some alternatives?
moko-resources - Resources access for mobile (android & ios) Kotlin Multiplatform development
android-buddy - Transform Android project classes with Byte Buddy at compile time
kotlin - The Kotlin Programming Language.
Gradle buildSrcVersions - Life is too short to google for dependencies and versions
gradle-lint-plugin - A pluggable and configurable linter tool for identifying and reporting on patterns of misuse or deprecations in Gradle scripts.
kotless - Kotlin Serverless Framework
scalroid - A scala-kotlin-java joint compilation plugin built on Gradle, for native Android.
android-maps-compose - Jetpack Compose composables for the Maps SDK for Android
android-stem - This is a Gradle plugin for Android applications that concatenates XML strings during compilation
gradle-recipes - Ready-to-use recipes for common build customizations that showcase the Android Gradle plugin's public APIs and DSL.
gradle-maven-publish-plugin - A Gradle plugin that publishes your Android and Kotlin libraries, including sources and javadoc, to Maven Central or any other Nexus instance.