This might be useful github.com/timmacp/AppEngineGwt/tree/main
Its based on github.com/tbroyer/gwt-maven-archetypes
& Google Cloud Platform samples for App Engine with Java 11+
github.com/GoogleCloudPlatform/java-docs-samples/tree/main/appengine-java11/appengine-simple-jetty-main
which
shows ho
Hi Thomas,
Aha!! You are correct, thank you - I have added it to my POM and now the
breakpoints are getting triggered :-)
Is there a way of limiting this configuration to a specific run
configuration, or sometning? The way I have it set up I think the flags are
passed every time?
com.google.
Hi Craig,
Ahh right, so although it's working at the moment with *appengine:run*
this is being phased out so I'd better be moving to a standalone server.
On Friday 28 June 2024 at 03:19:18 UTC+1 Craig Mitchell wrote:
> *> Only reason I ask is I've just had the app updated from java 7 because
>
Thanks for the suggestion Tim, I was really hopeful but I think I'm running
in the Debug perspective but the breakpoints are still not triggering :-(
On Thursday 27 June 2024 at 18:35:23 UTC+1 Tim Macpherson wrote:
> Did you open the debug view ? iirc in eclipse you need to
>
> Yahoo Mail: Searc
You need to pass the -agentlib:… as of the appengine plugin, as
it will fork a new JVM
https://cloud.google.com/appengine/docs/legacy/standard/java/maven-reference#appenginerun
On Thursday, June 27, 2024 at 7:15:26 PM UTC+2 dw...@cobwebb.com wrote:
> Hi,
>
> Can anyone help me get remote jdwp s
*> Only reason I ask is I've just had the app updated from java 7 because
Google dropped support - and the new project uses "appengine:run" for
running locally. Should we be doing it differently?*
Google are asking everyone to move to the "Second-generation Java
runtimes".
https://cloud.googl
Hi Craig,
On Wednesday 26 June 2024 at 02:56:31 UTC+1 Craig Mitchell wrote:
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
Thanks Ralph, So it's source map debugging in chrome for the client side,
jdwp remote debugging for the server side.
On Tuesday 25 June 2024 at 14:09:20 UTC+1 Ralph Fiergolla wrote:
> Hi! Unless you want to invest time and effort in getting eclipse plugins
> up and running, I would suggest us
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 migh
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,
Thanks Jens, I appreciate the answer, gives me something to have a go at.
Regards
Daniel.
On Monday 24 June 2024 at 11:20:15 UTC+1 Jens wrote:
> Debugging server code is done as usual using Java debug wire protocol
> (JDWP) remote debugging.
> Debugging client code is done using the browser dev
Debugging server code is done as usual using Java debug wire protocol
(JDWP) remote debugging.
Debugging client code is done using the browser dev tools which also allows
setting breakpoints. During development GWT CodeServer should be started
using '-style PRETTY -XmethodNameDisplayMode ABBREVI
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 tha
14 matches
Mail list logo