I was thinking along similar lines, but at compile time: 1. Include a list of deprecated public files in the release (we'll call it public-deprecated.txt). 2. Compiler gives a warning if anything from public-deprecated.txt is included in the compiled output. 3. Option to disable the warning (-noWarnPublicDeprecated). 4. Maybe an option to have the compiler specifically exclude any deprecated files from the compiled output (-excludePublicDeprecated)?
On Fri, Jan 16, 2009 at 12:15 PM, Ian Petersen <[email protected]> wrote: > > Would it be possible to engineer something that would throw up a > warning message in the hosted mode logger when the client requests one > of the deprecated files? Doing so probably wouldn't catch everybody > because -noserver users would presumably circumvent the check, but it > would probably catch a good chunk of the userbase. > > Ian > > > > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
