[GRADLE-404] jetty plugin should configure the JettyPluginWebAppContext even if supplied by build script Created: 18/Feb/09  Updated: 04/Jan/13  Resolved: 16/Apr/09

Status: Resolved
Project: Gradle
Affects Version/s: 0.5.2
Fix Version/s: 0.6

Type: Improvement
Reporter: Marcus Better Assignee: Hans Dockter
Resolution: Fixed Votes: 0

Attachments: File gradle-jetty-config.diff    


Build scripts that need fine-grained control over Jetty can assign the webAppConfig property in AbstractJettyRunTask. However, when this is done, AbstractJettyRunTask.configureWebApplication() will no longer use the task properties contextPath, tmpDirectory, webDefaultXml and overrideWebXml to configure the context, forcing build scripts to duplicate this code.

A better solution would be to always use those properties, regardless of whether the webAppConfig was created by the build script or not.

Build scripts could still retain full configurability of the web app by omitting the above-mentioned configuration properties.

Attaching suggested but untested patch.

Comment by Hans Dockter [ 16/Apr/09 ]

Patch applied. Thank you.

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