ServiceAsync is refreshed without changing Service

[ashouric]

Dear All,

When a project is associated with a VSS plugin, whenever I change anything, e.g. compiler settings that shouldn't affect existing code, Eclipse warns that all AsyncService are target of change, do you want to checkout or not.

I guess Designer is trying to refresh Async in some unneeded situations. it would be better to change Async only when the Service is changed.

Many thanks.

[Eric Clayberg]

When a project is associated with a VSS plugin, whenever I change anything, e.g. compiler settings that shouldn't affect existing code, Eclipse warns that all AsyncService are target of change, do you want to checkout or not.

I guess Designer is trying to refresh Async in some unneeded situations. it would be better to change Async only when the Service is changed.

This appears to be default Eclipse behavior.

Changing compiler settings triggers a full build of your project. Any Eclipse builders (including the Eclipse compiler and the GWT Designer Service builder) are triggered automatically and any derived resources are regenerated. Derived resource include your .classs file and your *ServiceAsync Java files.

We are looking into seeing whether there is a work around for this such as selectively disabling the Service builder during a full build.

[Eric Clayberg]

The latest GWT Designer build now includes a work around that will prevent our Service class builder from running during an Eclipse full build.