|Re: Republish required when Eclipse starts [message #208225 is a reply to message #208211]
||Wed, 06 February 2008 18:42
| Larry Isaacs
Registered: July 2009
David Matheson wrote:|
> I am using Eclipse 220.127.116.11 and WTP 2.0.1. I have a large web app
> configured with Tomcat 5.5.17. Every time that I start Eclipse I have
> to republish this web application, even if nothing has changed since I
> last left Eclipse. Does anyone else have this problem? I just wanted
> to ask before I filed a bug.
> Steps to reproduce:
> 1. Configure a web application with Tomcat (I used 5.5.17 and 6.0.13).
> 2. Publish application, note Status is Synchronized.
> 3. Exit Eclipse.
> 4. Start Eclipse.
> 5. Note that you have to republish the web application.
> Republishing a web app can take several minutes. I did not have to
> republish in previous versions of Eclipse and WTP.
This isn't a bug based just on the info provided. Eclipse can't assume
something didn't change in the web application outside of Eclipse while
Eclipse was stopped. Thus, some check would be needed to determine if
web application had changed. Rather that perform this check at startup,
it is incorporated into the publish. If the web application was
previously synchronized, then that publish shouldn't actually copy any
files and complete quickly.
Unfortunately due to Bug 206087, WTP 2.0.x may do a full publish by
mistake for the first publish after starting Eclipse. A fix is coming
in WTP 2.0.2. At startup, the web application will still say Republish,
but it should be a fairly fast publish that simply figures out you are
Powered by FUDForum
. Page generated in 0.03462 seconds