Yeah, for whatever reason, it is not easy to set up properly to run GWT inside IntelliJ. No idea why it has to be that way. No documentation either. I do have to say once it is done once, the set up is very consistent.
If and when they open source the plugin, I hope they open source the jetty plugin as well (the jetty plugin does not work properly for 12.0.17 and later as well. Given their focus right now, I am not optimistic it will ever get fixed), so that I can find out if it is possible to make it much easier to do. The ability to simply refresh the browser to get the up-to-date client code is just so convenient for me. On Tuesday, December 30, 2025 at 6:12:06 PM UTC-5 Craig Mitchell wrote: > I did install the Navigator extension for GWT. That worked well, and > handy if you use RPC. > > The JavaScript dubugger is another "you have it but you can't use it" > plugin: > [image: Screenshot 2025-12-31 100957.png] > > And when they say "more features", they really mean "all the features". 😆 > > On Wednesday, 31 December 2025 at 9:36:09 am UTC+11 Craig Mitchell wrote: > >> Thanks Khun. That looks way too hard! I think I'll stick with GWT Maven >> Plugin. 🙂 >> >> Turns out, the IntelliJ GWT plugin installs, but once I go back to see >> what's happening, I see this: >> [image: Untitled.png] >> >> So, IntelliJ actually isn't letting me use it. IntelliJ really should >> filter it out when searching, or at least say it won't work. >> >> On Wednesday, 31 December 2025 at 2:55:23 am UTC+11 Khun Yee Fung wrote: >> >>> I use the GWT plugin to run my GWT projects all the time. It is useful >>> for me because if I need to modify the client side code that is not used by >>> the server side, I can simply modify it and then refresh the browser to get >>> the up-to-date client code. This is especially nice when I am adjusting the >>> CSS and the look-and-feel. To get the CSS automatically refreshed, it has >>> to be injected somehow (I use StyleInjector.inject(), very nice to switch >>> to light/dark mode and back with CSS variables). It can't be in a file. If >>> it is in a file, then both jetty and GWT have to be re-run to get any >>> changes in the CSS file. I guess the CSS file is considered to be on the >>> server side, served by jetty. >>> >>> I also use the Jetty plugin to run the server side. Together, I can run >>> my GWT projects inside Intellij. >>> >>> If you are interested, I have an article on Medium on how to run the >>> whole thing with jetty 12.0 ( >>> https://medium.com/programming-is-life/how-to-run-jetty-12-and-gwt-inside-intellij-4a5e134bc397 >>> ). >>> >>> I don't use the JS debugger. >>> >>> On Tuesday, December 30, 2025 at 10:03:41 AM UTC-5 Jens wrote: >>> >>>> I use IntelliJ Ultimate and thus also using the GWT plugin. I don't use >>>> it to run GWT but instead use it for the enhanced code navigation, error >>>> checks, auto completion, etc.. But as far as I know you can only use it if >>>> you pay for Ultimate. However Jetbrains said in an issue that supporting >>>> the GWT plugin isn't priority anymore and they consider making it open >>>> source. I guess they have some metrics and the GWT plugin isn't used often >>>> enough these days. >>>> >>>> The JS debugger is ok, basically what you have in Chrome you then have >>>> in IntelliJ. I used it a few times but it annoyed me to always switch >>>> between browser and IDE if you put some breakpoints here and there and >>>> have >>>> to trigger them using the app UI in the browser. If I remember correctly >>>> the main benefit from debugging via IntelliJ was that you could navigate >>>> code more easily and thus peek at method implementations without actually >>>> entering them with the debugger. In the browser you cannot "click into" a >>>> method implementation while debugging as you only see a sourcemapped >>>> version of the original Java code. >>>> >>>> -- J. >>>> >>>> >>>> -- 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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/48a120e0-ac00-48c3-8a22-8c956703cd63n%40googlegroups.com.
