Eclipse Community Forums: Java Development Tools (JDT)

Help

Home

Home » Language IDEs » Java Development Tools (JDT) » Analyzing Sources Slow

Show: Today's Messages :: Show Polls :: Message Navigator

Analyzing Sources Slow [message #699630]

Fri, 22 July 2011 00:36

Tom

Messages: 4
Registered: July 2011

Junior Member

Just upgraded to Indigo. Now the "analysing sources" stage of building my project, which is re-triggered each time I alter a dependency, takes an inordinately long time (more than 5 minutes).

This is a GWT project. Not sure if that is relevant to the problem.

What is analysing sources doing? Why might it be slow? Has anything related changed from 3.6 -> 3.7?

Eclipse Indigo (3.7), Google Plugin for Eclipse 3.7, GWT SDK 2.3.0,
OpenJDK 1.6.0_22, Ubuntu 11.04 x84_64

Thanks

Report message to a moderator

Re: Analyzing Sources Slow [message #700930 is a reply to message #699630]

Sun, 24 July 2011 08:50

Martin Delemotte

Messages: 1
Registered: July 2011

Junior Member

Hi Tom,

I encounter the same problem with :

Eclipse Indigo (3.7), Google Plugin for Eclipse 3.7, GWT SDK 2.3.0,
Java(TM) SE Runtime Environment (build 1.6.0_25-b06), Fedora 15 i686

I also use the Scala Plugin (2.0.0.beta09) and Maven (m2e 1.0.0).

I thought it was due to a conflict between the Scala Plugin and Google Plugin for Eclipse. Do you use any other plugins yourself?

Report message to a moderator

Re: Analyzing Sources Slow [message #702170 is a reply to message #700930]

Tue, 26 July 2011 03:56

Tom

Messages: 4
Registered: July 2011

Junior Member

Over the weekend my build times have reduced! Perhaps we were having some network issues which were exacerbating the problem. However, it's still slow. I have tracked the cause down to repeated requests for the DTD document htp://dl.google.com/gwt/DTD/xhtml.ent that is referenced by each UI Binder template. I have 80 XML template files and the DTD doc is request 178 times during a clean build. The workaround I have found is to download and store this document locally and add it to the Eclipse XML Catalog. Doing this reduces my build time from approx. two minutes to under 15 seconds.

Wouldn't it be sufficient to fetch such things once per build?

Would be interesting to know if the previous GPE and Helios request this DTD so many times. (I used Wireshark to watch what was going on.)

Report message to a moderator