[GRADLE-669] Specify which logging libraries (app or gradle) to use with jetty tasks Created: 30/Sep/09 Updated: 30/Dec/16 Resolved: 30/Dec/16 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Jason Porter | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 4 |
| Description |
|
Mailing list discussion: http://www.nabble.com/Jetty-Logging-td25663786.html Jetty is using Gradle's logging libraries instead of 1) It's own or 2) libraries in the application. There should be a way to isolate the logging libraries Gradle is using and allow Jetty to it's own or one defined in the application. |
| Comments |
| Comment by Ryan Shillington [ 05/Nov/12 ] |
|
+1 I've spent hours trying to figure out how to configure jetty logging with gradle & SLF4J, only to find this. Ugh! I really want to configure jetty logging separately. Now I know it can't be done. |
| Comment by Benjamin Muschko [ 15/Nov/16 ] |
|
As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub. We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to. Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle! |
| Comment by Jochen Kemnade [ 16/Nov/16 ] |
|
Since the jetty plugin is deprecated, I guess this is a WONTFIX. |
| Comment by Benjamin Muschko [ 30/Dec/16 ] |
|
The Jetty plugin will be removed with Gradle 4.0 which means we won't work on a fix. Marking this issue "won't fix". |