This issue has other implications. When compiling very large JSPs, web containers can generate too much debug info and fail to compile with a "String too large error". The workaround is typically to set the suppressSmap parameter to true.

The only way I can see to do that in Jetty is to i) use a webdefault.xml file to set the value, or ii) configure the JspServlet in the app's web.xml. Option ii is not a possibility for us, so we can't currently run our app using the Gradle Jetty plugin.

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:

• Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
• Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

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.