Looks like third-party developers should work as before, but include your annotation processor into their build process. суббота, 8 октября 2016 г., 1:14:29 UTC+3 пользователь Ahmad Bawaneh написал: > > Dears, > We all know that GTW 3.0 will come with some major changes from the > current GWT, and so we find every were suggestions for how to be prepared > for these changes, and that is good, but here is my issue regarding the > removal of generators and the suggestion to replace them with Annotation > processors: > > I have been using generators to build some kind of registry, so a > developer can annotate a class with an annotation and using the generators > i generate the code that register that class in the registry to picked up > at run-time, which is the normal case here, but in my case developer write > there own modules in seperate projects and provides me with the final > artifact, and since in my generator i scan the class path i was able to > find the annotated classes within these third party jars and register them. > > that worked perfectly for me. > > now i have trying to replace my generators with annotation processors, but > annotation processors does not scan classes from third party jars as it > only works for source code, and now if i want things to work for me i have > to ask every one to write thier projects as part of my project - thier > projects source code should be part of my project -. > > and with this modularity is 100% been killed. > > So is APT the right choice? > or i am missing something and i am supposed to be able to make it work? > > > >
-- 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.
