Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Gradle plugin: detect all/more of logback possible user provided configuration
See original GitHub issueCurrently, only logback.xml file is detected. But logback support other configuration options:
Another issue is that existing logback detection is bound to hardcoded path (src/gatling/resources) and neglects options other than logback.xml, eg logback.groovy and logback-test.xml.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Gradle plugin: generate logback config even if there's ... - GitHub
Current issue Logback generation happens at doLast closure of processGatlingResources task. When there's no gatling resource, i.e. default ...
Read more >Logback error in Gradle - Help/Discuss
Logging system failed to initialize using configuration from 'null' java.lang.IllegalStateException: Logback configuration error detected:
Read more >Using Gradle Plugins
In this chapter we discuss how to use plugins and the terminology and ... 1, for core Gradle plugins or plugins already available...
Read more >Logging - Gradle User Manual
The log is the main 'UI' of a build tool. If it is too verbose, real warnings and problems are easily hidden by...
Read more >Developing Custom Gradle Plugins
This project produces and publishes a JAR which you can then use in multiple ... You can provide configuration for your plugin by...
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 Free
Top 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
Started working on the issue.
@eshepelyuk Github only parses the first line of the commit message to search for autoclose triggers.
fix: logback.xml detection and generation, close gatling/gatling#3951, close gatling/gatling#3952would have worked.