> The main question I have, though, is how to transition to such a > scheme? Users currently write explicit add-linkers all over the > place.
Since the choice of link style is an application, as opposed to library, kind of choice, and the switch is a one-liner, I propose that we break existing users in a helpful manner. 1) Add support for "deprecated" and "error" attributes to <module>, <define-linker>, <define-property>, <define-configuration-property>, <generate-with>, and <replace-with> tags - This allows messaging to be done up-front, instead of waiting for the entire link cycle. - The messages are emitted when the definitions are used with <add-linker>, <set-property>, or the rebind rule matches - Library developers also get some benefit in being able to turn-down existing .gwt.xml "API" 2) Whip up a quick tool to grep .gwt.xml files for the offending <add-linker> tag and replace it. - A sed script would be sufficient, although it leaves Windows users out in the cold. <define-linker name="xs" class="com.google.PrintErrorAndDieLinker" error="Replace <add-linker name='xs' /> with <set-property name='linker' value='xs' />" /> -- Bob Vawter Google Web Toolkit Team -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
