On 2012/05/30 16:35:33, jlabanca wrote:
That would involve creating 2.3-modified jars, syncing to the 2.4
release, and
running API Checker, just to update a file that is no longer used.
I'll leave
it for the next guy to worry about.
I meant reverting ("svn revert" or "git revert") some of the commits at
http://code.google.com/p/google-web-toolkit/source/list?path=/trunk/tools/api-checker/config/gwt23_24userApi.conf
(a priori r10356 and following commits; see
http://code.google.com/p/google-web-toolkit/source/list?path=/tags/2.4.0/tools/api-checker/config/gwt23_24userApi.conf
for comparison)
Even if it might not give an accurate result, that'd still be better
than what we have now, and be both a quick and easy "fix" (compared to
regenerating it as you proposed).
But you're probably right that it might not worth it.
http://gwt-code-reviews.appspot.com/1721803/
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
