Automattic / Automattic/configure
Change the logging level for plugin messages
- Dominant language
- Rust
- Stars
- 7
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
We should update our `println` messages to use proper log levels so they don't show up for every type of build. The most important one is the `Checking whether `configure` binary is present` [message](https://github.com/Automattic/configure/blob/trunk/gradle-plugin/configure/src/main/kotlin/com/automattic/android/configure/ConfigurePlugin.kt#L56) which shows up for even quiet (`-q`) builds.
https://docs.gradle.org/current/userguide/logging.html
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with gradle-plugin/configure/src/main/kotlin/com/automattic/android/configure/ConfigurePlugin.kt at line 56, then inspect the other println messages in that file. Read Gradle's logging documentation to identify suitable log levels. Done means plugin messages use appropriate levels and the configure-binary message no longer appears during quiet (-q) builds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100