Remove dependency on play.utils.Colors
See original GitHub issueLagom’s logback
project depends on Play just to use play.utils.Colors
.
Lagom even has a copy of play.utils.Colors
in ConsoleHelper.scala
.
🤦♂️
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Remove node-sass dependency #1986 - GitHub
I propose we should find another way of handling [css|sass|scss] until node-sass switches from using Gaze as their file watcher.
Read more >[Q] "google play services" requirement without gapps
Hi, I run OmniRom without gapps (with NOGAPPS actually) and there's an app that refuses to start with the error "google play services...
Read more >All com.android.support libraries must use the exact same ...
1) On navigation tab change it to project view · 2) Navigate to [YourProjectName]/. · 3) Delete all files starting with Gradle__com_android_support_[libraryName].
Read more >PackageManager - Android Developers
This exception is thrown when a given package, application, or component name cannot be found. interface, PackageManager.OnChecksumsReadyListener.
Read more >Learning the Basics - Gradle User Manual
If you add or remove a project that uses the Kotlin DSL, build script compilation fails if you forget to update a dependency....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think the path forward should be to remove Lagom’s
logback
module entirely in favor of using the one from Play. Lagom’sLogbackLoggerConfigurator
was copied from Play’s equivalent but the two have drifted apart since then. This should be reconciled.In the final project, yes. If I’m working on a library of reused code and I want to use Lagom-provided
logback
then I’m bloating it.