[GRADLE-1178] Enable the jetty plugin to use/overlay multiple webapp source directories. Created: 17/Oct/10  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 0.9.1
Fix Version/s: None

Type: Improvement
Reporter: Richard Bolkey Assignee: Unassigned
Resolution: Won't Fix Votes: 3


I have GWT output compiled to my build directory that I would like to expose when running the jettyRun task. There doesn't seem to be any good way to do this. I would like to add the output as an extra webAppSourceDirectory.

Comment by Richard Bolkey [ 21/Oct/10 ]

Found a way to perform this enhancement using 0.9-rc-1; but obviously, being able to do so with less code would be nice.

jettyRun.doFirst {
  jettyRun.webAppConfig = new JettyPluginWebAppContext()
  jettyRun.webAppConfig.baseResource = new ResourceCollection(
    ] as String[])
Comment by John Gibson [ 30/Nov/15 ]

I've found that Richard Bolkey's workaround doesn't work with Gradle 2.5. Specifically the ResourceCollection class isn't available on the build file's classpath. Trying to import the Jetty dependency manually as a build script dependency doesn't solve the issue. I'm guessing that the classloader handling for plugins has changed since 0.9.

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:

  • 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!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 11:48:58 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.