https://bz.apache.org/bugzilla/show_bug.cgi?id=66026
--- Comment #4 from Marvin Fröhlich <apa...@froehlich-mail.net> --- (In reply to Christopher Schultz from comment #3) > I believe this is your operating system "locking" JAR files. I have never > ever had a problem deleting, updating, replacing, patching, etc. JAR files > on Linux, but evidently on Windows it's generally not possible. This is true. The classloader doesn't release the jars. And on Windows this leads to these files being locked, on Linux it doesn't. I had to learn this myself when I switched to Windows. Though it's still the classloader, that induces this behavior. The WEB-INF/lib classloader doesn't do that. And I was surprised to see, that a custom webapp classloader doesn't behave the same way a WEB-INF/lib classloader does. This is the reason for this ticket. (In reply to Christopher Schultz from comment #3) > I wonder why you are checking assets out of revision-control directly into > the deployment directory of Tomcat. Or are you you using embedded Tomcat? Well, why not? It is the fastest way of synchronizing the webapp with development state on a dev machine. No, we're not using tomcat embedded. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
