Can retention policy of @GwtCompatible be changed to RUNTIME?
===

Folks,

Is there a specific reason for GwtCompatible interface to have `Retention policy = CLASS` ?

background:<br>
  we have project setup where an eclipse java project has code that is annotated with `@GwtCompatible` and code that is not. Building such a project uses different ANT targets. One such target segregates code that is annotated `@GwtCompatible` to be gwt-compiled later. We have an ANT Custom File Selector in place to do that segregation. in our build scripts. The selector is based on [this][1] description. Selector uses api: '`isAnnotationPresent`' to mark a java code file for selection. Such a selector doesn't seem to work because `GwtCompatible` has `Retention policy = CLASS`.

I'd like to know if retention policy of GwtCompatible can be changed to RUNTIME. Also, how else would you recommend tweaking the Custom selector so that annotation based selection can happen.

thanks,<br>
Chetan Kumar

  [1]: http://grokbase.com/t/ant/user/08apgzmbw6/aw-building-a-fileset-using-annotations