Re: [gwt-contrib] Asking for decision on DevMode embedded Jetty support

Ok, Sounds like we wouldn't be affected, we always run our stuff via TomCat with a one liner using the gretty Gradle plugin. -Mike On 4/15/21 10:07 AM, Thomas Broyer wrote: If you use the gwtSuperDev task, or if you use the

Re: [gwt-contrib] Asking for decision on DevMode embedded Jetty support

If you use the gwtSuperDev task, or if you use the gwtDev task but set noserver=true, then it won't impact you. You're then already starting another web server to serve your server-side code (and your host page). If you use the gwtDev task *and* did not set noserver=true, then you'd have to move

Re: [gwt-contrib] Asking for decision on DevMode embedded Jetty support

How would this impact Super Dev Mode in Gradle? We use Gradle with 'org.wisepersist:gwt-gradle-plugin:1.1.8'. On Thu, Apr 15, 2021, 09:56 Paul Robinson wrote: I used the built in Jetty server

Re: [gwt-contrib] Asking for decision on DevMode embedded Jetty support

Paul, What about the bookmarklet?. Is out working in your setup? On Thu, Apr 15, 2021, 09:56 Paul Robinson wrote: > I used the built in Jetty server until a year or so ago. Occasionally I > have to use the older version in development as we haven't upgraded > everybody in production to the new

Re: [gwt-contrib] Asking for decision on DevMode embedded Jetty support

I used the built in Jetty server until a year or so ago. Occasionally I have to use the older version in development as we haven't upgraded everybody in production to the new version yet. >From a development perspective, I find running a separate code server and Jetty to be much more productive.