Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Jetty 9 {java.home}/work not being honored

The support for ${jetty.home}/work was removed during the resolution of bug 294531

In this commit
From the WebInfConfiguration class

But all is not lost.

If you are deploying your WebApp via a Jetty context deployable, you can set the specific temp directory for your specific webapp this way...

<?xml version="1.0"  encoding="ISO-8859-1"?>
<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"
<Configure class="org.eclipse.jetty.webapp.WebAppContext">
  <Set name="contextPath"><Property name="foo"/></Set>
  <Set name="war">/var/web/webapps/foo.war</Set>
  <Set name="tempDirectory"><Property name="jetty.home"/>/work/foo</Set> <!-- Set this -->

Note: that this functionality is a bit different than ${jetty.home}/work
As ${jetty.home}/work was the parent directory for the tempDirectory.

If you feel the ${jetty.home}/work is important still, please, file a bug asking for it back.
Note that any implementation for this would be for ${jetty.base}/work, not ${jetty.home}/work 

Joakim Erdfelt <joakim@xxxxxxxxxxx>
Expert advice, services and support from from the Jetty & CometD experts

On Tue, Dec 3, 2013 at 8:27 AM, pkcinna <pkcinna@xxxxxxxxx> wrote:
After upgrading to Java 7/Jetty 9.1.0.v20131115,  my webapps keep getting
expanded in /tmp even though I added a /opt/jetty/work (jetty installed in
/opt/jetty).  Is this a bug?  How can I debug this to make sure the default
installation is not explicitly configured to use or

View this message in context:
Sent from the Jetty User mailing list archive at
jetty-users mailing list

Back to the top