[GRADLE-1901] Allow access to gradle's internal jetty classes for customization of Jetty tasks Created: 08/Nov/11 Updated: 16/Jan/17 Resolved: 16/Jan/17 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 1.0-milestone-5 |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Luke Taylor | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Description |
|
See support ticket #1056. Classloader isolation means that it is no longer possible to create Jetty connectors etc for customization of the Jetty tasks. Adding jetty to the buildscript classpath is a fragile solution as it isn't possible to know up-front the version of Jetty used internally in a gradle installation. It would be useful if there was a way to access the internal Jetty configuration (similar to localGroovy()). An alternative might be to allow the user to create a Jetty configuration in their build script and have gradle use that. |
| Comments |
| Comment by Luke Taylor [ 08/Nov/11 ] |
|
For reference, the current suggested workaround is as for |
| 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 Benjamin Muschko [ 16/Jan/17 ] |
|
The Jetty plugin has been deprecated and is scheduled to be removed with Gradle 4.0. We are not going to work on this issue anymore. |