I had this same problem - but it was solved with the
useFileMappedBuffer=false solution. One difference was that I didn't change
/etc/webdefault.xml - I actually copied webdefault.xml into my project and
updated my pom file:
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
<configuration>
<contextPath>/bingo</contextPath>
<scanIntervalSeconds>3</scanIntervalSeconds>
<webDefaultXml>src/main/config/jetty/webdefault.xml</webDefaultXml>
<connectors>
<connector
implementation="org.mortbay.jetty.nio.SelectChannelConnector">
<port>9090</port>
<maxIdleTime>60000</maxIdleTime>
</connector>
</connectors>
</configuration>
</plugin>
If it isn't clear, I use jetty:run ala maven from within my Eclipse
environment. Obviously, every project ends up with a copy of webdefault.xml,
but otherwise it turned out to be a straightfoward fix.
-Luther
On Wed, Oct 28, 2009 at 11:02 AM, Felix Gonschorek <fe...@ggmedia.net>wrote:
> Hi Inge,
>
> one of our developers had the same issues (eclipse, jetty, maven) on
> windows XP - we tried several configurations (including the disabled jetty
> lock) without success. the problem disappeared after a fresh install of
> windows xp; we could not get rid of the problem with in any other way (tried
> several jetty configurations, re-installed eclipse and jre, disabled
> locking, ...)
>
> the lock occured on css files.
>
> the problem has not occured on linux or mac development machines.
>
> just to let you know, that you are not alone with this problem :)
>
>
> felix
>
> Inge Solvoll schrieb:
>
> Hi!
>>
>> I'm having problems with my development environment.
>>
>> First of all: I have set the useFileMappedBuffer=false in
>> /etc/webdefault.xml
>>
>> My problem is that Tapestry 5 Javascript files located in WEB-INF/classes
>> and subfolders are locked by Jetty. This prevents eclipse from deleting
>> WEB-INF/classes to do a rebuild after I make a change in a java file. The
>> end result is that most class files are deleted and not rebuilt, so I have
>> to stop jetty, do a manual rebuild, and then start Jetty again. This if,
>> of
>> course, a disaster for me...
>>
>> Does anyone here have a clue on how to prevent Jetty from locking the
>> resource files in WEB-INF/classes?
>>
>>
>>
>
