btw: "appengine:run" is deprecated. You won't be able to do any updates to your app until you upgrade. https://cloud.google.com/appengine/docs/legacy/standard/java/maven-reference But you probably already knew this. 🙂
On Wednesday 26 June 2024 at 11:23:00 am UTC+10 Craig Mitchell wrote: > As Ralph says, for the client, you can use the Chrome debugger, but if you > didn't want to, the Eclipse SDBG plugin should still work. Or if you use > IntelliJ, the paid Ultimate version comes with a JS debuger (I've not seen > a JS debugger for the free Community version). > > For the server, you might find it easier to put the flags Ralph talks > about into your pom file. Eg: If you use springboot, you can do this: > > <plugin> > <groupId>org.springframework.boot</groupId> > <artifactId>spring-boot-maven-plugin</artifactId> > <executions> > <execution> > <goals> > <goal>repackage</goal> > </goals> > </execution> > </executions> > <configuration> > <skip>false</skip> > <jvmArguments> > -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000 > <!-- > Allow debugging --> > --add-opens java.base/java.lang=ALL-UNNAMED <!-- Allow exceptions > to have java.lang details serialised --> > </jvmArguments> > </configuration> > </plugin> > > On Tuesday 25 June 2024 at 11:09:20 pm UTC+10 Ralph Fiergolla wrote: > >> Hi! Unless you want to invest time and effort in getting eclipse plugins >> up and running, I would suggest using your browser's development tools >> (Ctrl+Shift+I in Chrome/Edge) to debug the client side. Thanks to source >> maps it will show your JAVA source code when debugging. >> To debug the server side, you need to start your server with "-Xdebug >> -Xrunjdwp:server=y,transport=dt_socket,address=8000,suspend=n" and create a >> debug configuration to connect to port 8000 in Eclipse. >> Good luck >> Ralph >> >> On Mon, Jun 24, 2024 at 11:19 AM 'Daniel Webb' via GWT Users < >> [email protected]> wrote: >> >>> Hi, >>> Is it possible to debug GWT projects - setting breakpoints and stepping >>> through code? This would be server and/or client debugging. >>> >>> We've just had our internal GWT based app updated and it now uses maven >>> to run (clean install appengine:run). The eclipse plugin based debugging >>> technique that I used to use no longer seems to work. >>> >>> Thanks for any advice, I really like GWT but I'm lost as to how it all >>> works! >>> Daniel >>> >>> -- >>> 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 on the web visit >>> https://groups.google.com/d/msgid/google-web-toolkit/253e328a-484c-4c19-aaf7-e489780c3c0bn%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/google-web-toolkit/253e328a-484c-4c19-aaf7-e489780c3c0bn%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- 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 on the web visit https://groups.google.com/d/msgid/google-web-toolkit/f50a45fa-71f7-45e9-ba29-29f8d66adf5bn%40googlegroups.com.
