[gwt-contrib] Re: Asking for decision on DevMode embedded Jetty support
Removal of embedded Jetty from DevMode sounds sensible and I would normally agree. However, I am working as an architect for a global organization with many projects build on GWT and our development process relies heavily on DevMode and embedded Jetty. Removing embedded Jetty will make the work for our developers more difficult because they will have to perform at least 5 steps to run our applications on their PCs compared to just 1 at the moment. This is going to raise quite a few eyebrows across the enterprise and decrease the productivity of our developers. I also expect that we are not only the only organisation with GWT codebases and other teams equally rely on DevMode and embedded Jetty.. I vote for removal of support for Java7 and adjustment of the GWT classpath to align with embedded Jetty classpath, under GWT 2.9.0 and so forth in the future. Please don't force us to change our ways unnecessarily. On Tuesday, 13 April 2021 at 16:16:51 UTC+1 frank.h...@googlemail.com wrote: > I agree with Jens. I would - also - vote for the removal. > > Besides the things Jens mentioned, we have Thomas Broyer's > gwt-maven-archetype (for Jetty/Tomcat) or the > gwt-maven-springboot-archetype (for Spring Boot) to generate Maven multi > module projects. So, it is quite easy to generate a multi module project. > And it is well documented and maintained. > > I would prefer spending some times on updating gwtproject.org (the part > of how to start) instead of udpating the Jetty stuff. > > I know, that there are many single module projects outside that run with > devmode. I moved sereval of them to a new project structure inn the last > years. In many cases this is not really hard to do. > > > > > Jens schrieb am Sonntag, 11. April 2021 um 23:04:13 UTC+2: > >> For reference: >> >> Jetty ASM issues: >> https://github.com/gwtproject/gwt/issues/9606 >> https://github.com/gwtproject/gwt/issues/9693 >> https://github.com/gwtproject/gwt/issues/9720 >> >> Jakarta servlet support question: >> https://github.com/gwtproject/gwt/issues/9727 >> >> Other embedded Jetty related issues: >> jrt: URLs not recognised with Java 9+: >> https://github.com/gwtproject/gwt/issues/9582 >> Class loader leak protection code causes (ignorable, yet annoying) error >> logs in Java 9+: https://github.com/gwtproject/gwt/issues/9561 >> >> >> >> >> -- 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/60735ae0-d52e-4282-aeef-2ec6ffe2ad64n%40googlegroups.com.
[gwt-contrib] Re: Asking for decision on DevMode embedded Jetty support
I agree with Jens. I would - also - vote for the removal. Besides the things Jens mentioned, we have Thomas Broyer's gwt-maven-archetype (for Jetty/Tomcat) or the gwt-maven-springboot-archetype (for Spring Boot) to generate Maven multi module projects. So, it is quite easy to generate a multi module project. And it is well documented and maintained. I would prefer spending some times on updating gwtproject.org (the part of how to start) instead of udpating the Jetty stuff. I know, that there are many single module projects outside that run with devmode. I moved sereval of them to a new project structure inn the last years. In many cases this is not really hard to do. Jens schrieb am Sonntag, 11. April 2021 um 23:04:13 UTC+2: > For reference: > > Jetty ASM issues: > https://github.com/gwtproject/gwt/issues/9606 > https://github.com/gwtproject/gwt/issues/9693 > https://github.com/gwtproject/gwt/issues/9720 > > Jakarta servlet support question: > https://github.com/gwtproject/gwt/issues/9727 > > Other embedded Jetty related issues: > jrt: URLs not recognised with Java 9+: > https://github.com/gwtproject/gwt/issues/9582 > Class loader leak protection code causes (ignorable, yet annoying) error > logs in Java 9+: https://github.com/gwtproject/gwt/issues/9561 > > > > > -- 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/35490456-4697-47bf-8537-7c46609bc346n%40googlegroups.com.
[gwt-contrib] Re: Asking for decision on DevMode embedded Jetty support
For reference: Jetty ASM issues: https://github.com/gwtproject/gwt/issues/9606 https://github.com/gwtproject/gwt/issues/9693 https://github.com/gwtproject/gwt/issues/9720 Jakarta servlet support question: https://github.com/gwtproject/gwt/issues/9727 Other embedded Jetty related issues: jrt: URLs not recognised with Java 9+: https://github.com/gwtproject/gwt/issues/9582 Class loader leak protection code causes (ignorable, yet annoying) error logs in Java 9+: https://github.com/gwtproject/gwt/issues/9561 -- 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/9fad99cf-9d54-4550-b740-210a6c9175d9n%40googlegroups.com.
