Well said. Allow me to explain what I meant by saying "we shouldn't be forced to change our ways unnecessarily."
Following past discussions and the current conversation, I felt that there is a push by certain people towards removing Jetty support from GWT to ease the maintenance pains and without replacing it with something equivalent. This is going to be disruptive for the teams in the organization I work for and probably many other teams worldwide. I expect the current technology to be preserved the way it is so that we can keep following our current development recipes without disruption or productivity impact. This implies IMO that Java7 support has to be dropped and the GWT classpath has to be aligned and kept being aligned going forward with that of a more recent Jetty version, until such time that we reach a dead end and this construct cannot be maintained anymore. On Saturday, 17 April 2021 at 14:58:37 UTC+1 [email protected] wrote: > Hi all! > > I don’t get this particular statement: > > Until then we shouldn't be forced to change our ways unnecessarily. > > > This is not limited to [email protected] ’s last email but to many > comments here on this list/group. > > Nobody is forced to change any way. > > In my opinion: > Just stick to the current version of GWT and the toolchain you use at the > moment. > > But for future releases, be it GWT 3.0, GWT 2.10, GWT 2.9.x, J2CL or > whatever you call it, let’s drop the support for old/outdated/„cumbersome“ > technologies/versions/products etc. so that all the other developers can > use modern tools and the guys who maintain/develop GWT and all the other > plugins/IDEs/tools in this ecosystem for us do not have to bother about > this old stuff. Let’s move forward!! > > Don’t get me wrong, I really understand that many enterprises maintain big > GWT applications which are running for many years now and will run for many > more and these have to be supported. > But nobody takes the existing tools away. Just stick to the current > version and you are good. > > Just my 50 cent, without - hopefully - annoying someone. > > Thank you! > > > > > On Friday, 16 April 2021 at 16:07:28 UTC+1 [email protected] wrote: > >> On Fri, Apr 16, 2021 at 3:12 PM Vassilis Virvilis <[email protected]> >> wrote: >> >>> That's great news to hear. Is there any doc about this? >>> >> >> It's been there since 2.7, *checks notes* more than 6 years ago. >> Either pass `-launcherDir` to CodeServer, or use DevMode, which defaults >> to using that (legacy DevMode has to be explicitly reenabled through >> -nosuperDevMode) >> See http://www.gwtproject.org/articles/superdevmode.html >> >> >>> How does it know when to switch between codeserver and production code? >>> >> >> A stub nocache.js file is generated (overwriting your production one if >> you use the same dir) that will trigger a recompile on the CodeServer and >> load the generated script, similar to clicking the bookmarklet. >> >> What we're talking about here is more or less about removing DevMode "as >> we know it" that directly serves a web app following the "exploded WAR" >> layout, and only keeping the CodeServer; or possibly serve static files >> from DevMode but no longer host servlets et al. >> The issue here is conflicts between Jetty/DevMode and the project's >> server-side dependencies in the classpath (due to a project with mixed >> client and server code, and the fact that we have a custom >> WebAppClassLoader that loads from both the WEB-INF/classes+WEB-INF/lib and >> the classpath), and even conflicts between Jetty and the WEB-INF/lib, and >> of course issues with the version of ASM from GWT used by Jetty to scan the >> webapp classloader when it encounters module-info.class files. >> >> -- >> Thomas Broyer >> /tɔ.ma.bʁwa.je/ <http://xn--nna.ma.xn--bwa-xxb.je/> >> > > -- > You received this message because you are subscribed to the Google Groups > "GWT Contributors" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-web-toolkit-contributors/16974302-ff52-4fc0-bcf7-4c25356e708en%40googlegroups.com > > <https://groups.google.com/d/msgid/google-web-toolkit-contributors/16974302-ff52-4fc0-bcf7-4c25356e708en%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > > -- > schubec GmbH > DI (FH) DI Bernhard Schulz > Dreifaltigkeitsgasse 18 > 5020 Salzburg > Austria / EUROPE > > Tel: +43 699 19337476 <+43%20699%2019337476> > Mail: [email protected] > URL: https://www.schubec.com > Skype-Username: schubec > > Geschäftsführer der schubec GmbH: DI (FH) DI Bernhard Schulz > Sitz der Gesellschaft: 5020 Salzburg > Firmenbuchnummer: FN383758a > Steuernummer: 1584886 > UStID: ATU67395366 > > Impressum: > https://www.schubec.com/de/impressum.php > > -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/06873808-518b-4b63-9289-646d18807c98n%40googlegroups.com.
