Hi Guys, 

today I ran into the ole Jetty locking resource again because I started doing 
some Javascript. Howard had responded two years ago:

> I've hit this problem too, on a client's project using RunJettyRun. 

> The solution is to move classpath resources from src/main/java (or 
> equivalent) to src/main/resources (or equivalent) and add 
> src/main/resources as a class folder.  Thiis keeps Eclipse from trying 
> to copy the files (from src/main/java to classes) when they change and 
> that seems to keep everyone happy.


While this works you won't have the resources folder with neat collapsed 
packages as the source folders have.

I'm writing because I have reproduced the exact same issue with a file in 
resources that get's loaded by my own code. When I changed the code to properly 
close the input stream this problem disappears. Is it possible that tapestry 
just doesn't release the input streams it holds on .js files?


Kind Regards,
Wulf

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to