I am grabbing the opportunity to summarize by emphasizing the following: 1. IMO DevMode+Jetty should NOT be removed because it is still being is use, particularly by enterprise teams.
2. DevMode+Jetty has always been a very good selling point for GWT since its birth. If you want to remove DevMode+Jetty you have to provide a replacement and I have only read about removal so far. 4. Removal of support for Java 7 is more than welcome and tolerable it seems as it is not being used by projects anymore. Also projects that are still using Java7 should move to Java8+ regardless. 5. I accept that people still using DevMode+Jetty , like teams in the enterprise I work for, may have to consider a transformation in the future as soon as we reach a dead end, but not just yet. 6. Considering, all of the above. I suggest dropping Java7 support, aligning the GWT classpath with Jetty classpath and keep doing so until we reach a dead end, then we can consider making any kind of disruptive changes (like replacing DevMode+Jetty). Until then we shouldn't be forced to change our ways unnecessarily. 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.
