You dont need to maintain a separate branch or code base, you can use the latest snapshot which is as stable as a release, i am pretty sure when 2.9 is release you will only need to switch version and everything still works, if you can use the snapshot for some reason you can use the unofficial release as discussed here https://groups.google.com/forum/#!topic/google-web-toolkit/qmwiMVofhR8/discussion or you can fork and release internally.
and the community work, we need to know that the active members in the community is small, that is said we could have made a GWT3.0 a lot earlier, we could have focused in shipping a working maven plugin for j2cl and call the day, but most of the efforts is focused in making sure that old apps will be able to migrate to gwt3.0 without much effort and this part in specific is very important and very hard and consumes a lot of time, GWT apps in general are big apps and making GWT3.0 that only works for new apps only or requires app rewrite does not make any sense. to get more insight on what have been done check this list https://ci.vertispan.com/ On Wednesday, February 19, 2020 at 3:21:03 PM UTC+2, Luis Fernando Planella Gonzalez wrote: > > It has always been said that GWT is active when similar questions are > asked in the forum. > However, given that the last version, 2.8.2, was released on Oct 19, 2017 > and was a bugfix for the 2.8.0 version, released on Oct 20, 2016, I can't > see it as "active". > At least it smells bad! > Even the 1.0 release of Elemental can't be used, because it requires newer > components than the pre-packaged version. > It is a sad thing, because I work on a large project using GWT since its > 1.5.0 version, and our project is actively developed and still evolving. > I hope GWT 2.9 is out "soon", because we're planning to switch to Java 11 > in the coming months, and it would be a burden to maintain a separated Java > version only for the frontend part (been there, done that with Java 8). > The fact is that since Google left the project, things are way too slow. > Understandable, as it is based on best effor from the brave developers, > but still disheartening. > Still, I don't loose hope that GWT will be still maintained. > > Em terça-feira, 18 de fevereiro de 2020 12:08:40 UTC-3, Jeff Zemsky > escreveu: >> >> Frank - Thanks for the reply, but it would be good to understand the >> plans to complete the GWT 2.9 release - particularly with reference to Java >> 11 support. Any insight there? >> >> On Monday, January 27, 2020 at 4:23:09 AM UTC-5, Frank Hossfeld wrote: >>> >>> Atm the community is very active. We are working on GWT modules: >>> replacing generators and JSNI, testig the migraed moules against J2CL, etc. >>> Besides that, many new frameworks are evolving. >>> >>> Take a look at this rooms: >>> https://gitter.im/gwtproject/gwt >>> https://gitter.im/vertispan/j2cl >>> https://gitter.im/DominoKit/domino >>> to get more infos. >>> >> -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/c49cad20-7392-449c-a7cc-cf28016e1b44%40googlegroups.com.
