Gradle Jetty plugin locking files

Question

Is there a way to fix the file locking issue caused by `jetty` entirely from `gradle`? Some clarification: When using the Gradle Jetty plugin by running `gradle jettyRun,` jetty causes the static resource files (html, css, js, etc.) to be locked when using Windows. You can see a description of the problem in Files locked on Windows. The same article also describes how you can fix that. Basically you have to either: - Disable the use of file mapped buffer - Not use NIO at all. Both things require to add some jetty specific configuration files to the project, which I do not want to do - the jetty plugin is used only for convenience, and maintaining configuration for it does not feel right. I do not need NIO for testing on the local machine, so any solution works. Edit: For now, I picked the option at which you set `useFileMappedBuffer` to `false`. This is how to do it: Specify a path to your `webdefault.xml` like ``` [jettyRun, jettyRunWar,jettyStop]*.with { //other configs webDefaultXm…

Accepted Answer

Kiril answered his own question, many thanks. You should follow Kiril's instructions and this will help you find the appropriate `webdefault.xml`.

To find out what version of Jetty is started by Gradle, execute

```
gradle jettyRun -i
```

And you'll see something like this:

```
...
Tmp directory =  determined at runtime
Web defaults = org/mortbay/jetty/webapp/webdefault.xml
Web overrides =  none
Webapp directory = C:\dev\my-project\src\main\webapp
Starting jetty 6.1.25 ...
jetty-6.1.25
...
```

It took me a while to find a copy of Jetty 6.1.25 as it is no longer listed on the Jetty download page (not even in the archive section!).

You can then grab the appropriate copy of `webdefault.xml` from here, adjusting the version number as appropriate for your needs:

http://grepcode.com/file/repo1.maven.org/maven2/org.mortbay.jetty/jetty/6.1.25/org/mortbay/jetty/webapp/webdefault.xml

Gradle Jetty plugin locking files

Solution

Problem