> Is there a solution to tell GWT that my ClientBundle needs to be refreshed > at every compilation? >
No. Also your solution defeats any code pruning because of the generated switch statements that references all the component templates that might or might not be used by a given application. You should provide a predefined ClientBundle that has one method per component that returns the matching TemplateResource. Your library users would then create their own ClientBundle for their own templates or use the default ones. Basically it's very much like defining lots of ImageResource methods on a ClientBundle to provide images in an optimizable way. Also if you want your library to work in a post GWT 2.8 world, then you might want to consider an APT based solution as GWT 3.0 will likely not support GWT generators anymore. -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
