Eclipse Analyzing Sources Slow

[gutto]

Hi

Has anyone ever encountered the "analyzing sources" stage of an
eclipse build taking an inordinately long time? It seems to be
required each time I make a change to the dependencies of the project.
It takes roughly 5 minutes, which is unacceptable.

Does anyone know what is happening during this stage? I'm assuming its
building Eclipse metadata or something. Can you suggest what I might
try to find the cause of the slow running?

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

[Alex Luya]

Same problem here,even reusing old workspace

On Jul 22, 6:55 am, gutto <thomas.gutteri...@gmail.com> wrote:
> Hi
>

> Has anyone ever encountered the "analyzingsources" stage of an

["Ionuț G. Stan"]

I've had the same problem and the times improved a bit after downgrading
to Eclipse Helios. It seems there are some problems with Indigo.

--
Ionuț G. Stan | http://igstan.ro

[gutto]

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 http://dl.google.com/gwt/DTD/xhtml.ent that is referenced
by each UI Binder templates. 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.)

On Jul 23, 1:18 am, "Ionuț G. Stan" <ionut.g.s...@gmail.com> wrote:
> I've had the same problem and the times improved a bit after downgrading
> to Eclipse Helios. It seems there are some problems with Indigo.
>
> On Jul/22/2011 14:36, Alex Luya wrote:
>
>
>
>
>
>
>
>
>
> > Same problem here,even reusing old workspace
>

> > On Jul 22, 6:55 am,gutto<thomas.gutteri...@gmail.com>  wrote:

[Thomas Broyer]

On Tuesday, July 26, 2011 5:54:28 AM UTC+2, gutto wrote:

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 http://dl.google.com/gwt/DTD/xhtml.ent that is referenced
by each UI Binder templates. 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.)

They did: http://code.google.com/p/google-web-toolkit/issues/detail?id=5265

Maybe not that many times, and a priori not at the same time (not when building the project, but when opening the XML files), but still. 

[gutto]

Thanks, that's interesting. Obviously related. I had noticed that
content assist in templates is slow the first time I tried to use it.
I was quite pleased to see that in Indigo it will actually auto-
complete, whereas in Helios it did nothing when I selected an entry
from the suggestion list.

On Jul 26, 8:17 pm, Thomas Broyer <t.bro...@gmail.com> wrote:
> They did:http://code.google.com/p/google-web-toolkit/issues/detail?id=5265

> Maybe not that many times, and *a priori* not at the same time (not when

[gutto]

Pulled down an update for GPE today.

Google Plugin for Eclipse 3.7 2.3.3.r37v201107211953
com.google.gdt.eclipse.suite.e37.feature.feature.group Google, Inc.

Problem appears to have disappeared!

[Alex Luya]

I have installed this one,but problem still existed.

[gutto]

Hmm, all I can suggest is that you try the XML Catalog workaround.

[Alex Luya]

After removing all WindowBuilder related packages,everything works fine.