> About GWT generators not being supported anymore, does this include the > ClientBundle? The generators I overridden (*AbstractResourceGenerator*) > is heavily used in ClientBundle (like for TextResource etc..), and I didn't > think they were going to remove that. >
All stuff that is based on GWT generators needs to be rewritten. Some stuff is easy (e.g. GWT Places, see https://github.com/tbroyer/gwt-places ), other stuff requires modifications. I guess ClientBundle belongs to this category because it likely requires a new annotation on the interface that extends ClientBundle to make it visible to some APT generator. But the general way ClientBundle works probably stays the same because all required information is defined in the interface. The only downside is that APT does not run when a resource is changed, so it need to be started through some other means then or you need a different tool that converts the resource to some annotated java file. -- J -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
