Description Andrey Melentyev 2010-10-11 06:39:32 EDT

Build Identifier: 20100617-1415

I have a dynamic web project (v2.5) with JSF 2.0 facet which has four dependencies (utility projects). When I edit some JSP or XHTML file from the web project and perform publish on the Tomcat 7.0.2 server the web app context is reloaded. 

Looks very similar to the case described in http://wiki.eclipse.org/WTP_Tomcat_FAQ#Why_does_my_context_reload_after_I_publish_a_change_that_only_involves_a_changed_JSP.3F

The difference is that:
1) I'm using the most recent stable version of Eclipse and WTP and not the one described in the link.
2) I tried using custom server location instead of Tomcat installation.

Some additional info which might be helpful or not:

After the publish event the jars with utility projects are updated in WEB-INF/lib directory. Even if there were no changes to those projects. Interesting thing is that not all utility project jars are updated, only three of four.

The bug is quite annoying because we have much work to do on UI level and context reload takes a while (we have a huge Spring context and long-running app initialization). 

Please let me know if some information is missing from description. Unfortunately I can not provide an example since our application is closed-source.

Any hint for debug steps and/or workaround will be helpful.

Reproducible: Always

Steps to Reproduce:
1. Change some JSP/XHTML file in dynamic web project
2. Publish the changes to Tomcat
3. See that the context is reloaded.