paranoid
dependency-analysis-gradle-plugin
| paranoid | dependency-analysis-gradle-plugin | |
|---|---|---|
| 1 | 9 | |
| 660 | 1,606 | |
| - | - | |
| 0.0 | 9.6 | |
| over 2 years ago | 9 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.
paranoid
-
Any good alternative to StringCare and Paranoid libraries, to obfuscate important keys
So far I've known just 2 libraries that do it (StringCare and Paranoid), but once every few versions I notice issues, either in building or that it won't work as it's supposed to.
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?
AndroidLibrary - Android library to reveal or obfuscate strings and assets at runtime
android-buddy - Transform Android project classes with Byte Buddy at compile time
moko-resources - Resources access for mobile (android & ios) Kotlin Multiplatform development
RocketX - 🔥🔥 android 端编译加速插件🚀 动态识别未改动 module 并在编译流程中替换为 aar ，只编译改动模块，加速 Android apk 的编译速度。
secrets-gradle-plugin - A Gradle plugin for providing your secrets to your Android project.
Catalog - Generate type-safe, user-friendly extensions to resolve Android resources.
gradle-lint-plugin - A pluggable and configurable linter tool for identifying and reporting on patterns of misuse or deprecations in Gradle scripts.
Gradle buildSrcVersions - Life is too short to google for dependencies and versions
scalroid - A scala-kotlin-java joint compilation plugin built on Gradle, for native Android.
android-stem - This is a Gradle plugin for Android applications that concatenates XML strings during compilation
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.