Filed https://bugs.eclipse.org/bugs/show_bug.cgi?id=423060
-- Joakim Erdfelt <[email protected]> webtide.com <http://www.webtide.com/> - intalio.com/jetty Expert advice, services and support from from the Jetty & CometD experts eclipse.org/jetty - cometd.org On Tue, Dec 3, 2013 at 1:50 PM, Paul C <[email protected]> wrote: > Thanks. My opinion is having the work dir makes it easy to setup on > servers shared by many users or there are multiple jetty installs. > Convention over configuration usually makes for a better design so it seems > worth bringing back work dir support... will vote for it. > On Dec 3, 2013 8:12 AM, "Joakim Erdfelt" <[email protected]> wrote: > >> The support for ${jetty.home}/work was removed during the resolution of >> bug 294531 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=294531> >> >> In this commit >> >> https://github.com/eclipse/jetty.project/commit/9d756dc018de2af33dfd3fd4e307427e7b6f441e#diff-082f6e6d42ec2fd940a1000fe544228b >> 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" >> " >> http://www.eclipse.org/jetty/configure_9_0.dtd";> >> <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 --> >> </Configure> >> >> 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<https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Jetty&format=guided> >> . >> Note that any implementation for this would be for ${jetty.base}/work, >> not ${jetty.home}/work >> >> >> -- >> Joakim Erdfelt <[email protected]> >> webtide.com <http://www.webtide.com/> - intalio.com/jetty >> Expert advice, services and support from from the Jetty & CometD experts >> eclipse.org/jetty - cometd.org >> >> >> On Tue, Dec 3, 2013 at 8:27 AM, pkcinna <[email protected]> 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 java.io.tmpdir or >>> something? >>> >>> >>> >>> -- >>> View this message in context: >>> http://jetty.4.x6.nabble.com/Jetty-9-java-home-work-not-being-honored-tp4961702.html >>> Sent from the Jetty User mailing list archive at Nabble.com. >>> _______________________________________________ >>> jetty-users mailing list >>> [email protected] >>> https://dev.eclipse.org/mailman/listinfo/jetty-users >>> >> >> >> _______________________________________________ >> jetty-users mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/jetty-users >> >> > _______________________________________________ > jetty-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/jetty-users > >
_______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
