Note that such a project would use the org.gwtproject:gwt BOM, but the com.google.gwt:gwt-user and com.google.gwt:gwt-dev libraries
right, and when it updates the o.g bom, would correctly move c.g.g -> o.g libraries
yes (through relocations), but the project itself should then depend on org.gwtproject:gwt-user directly (rather than relying on the relocation)
could i ask you to post such a summary on the mailing list, as a way to bring the topic up again, and we can make these changes in the repo in anticipation of a release? i also notice that you have a htmlunit/jetty/asm patch that you might want to merge, i have a draft, doesn't make sense for us to conflict on that (but i'll certainly assist in testing your commit if you'd like to proceed)
So, first step: use org.gwtproject:gwt:2.9.0 BOM; then when updating: update to org.gwtproject:gwt:2.10.0 and change direct dependencies from com.google.gwt to org.gwtproject.
migration to org.gwtproject, dealing with degraded debugging experience in chrome, updated dependencies seems like a good 2.10 to aim for - i also have that remotewebdriver runstyle that could be worth putting into gwt proper
(there is also a kotlin backend now too - ostensibly your java can be passed through j2cl to emit kotlin sources)
@rdeangelis83 i'm sorry, i didnt get around to finishing something, but i'll put up a gist if you want to try what i did sketch out - i think the structure is right, but i didn't get the chance to validate it
Rocco De Angelis
@niloc132 THX 🙏🏻 I will give it tomorrow a try
always wondered how much of blazor output is actually wasm, especially considering the question of GC.
how can I debug server side in a project with client/shared/server ?
how to attach a debugger ?
I have a dead lock situation and I have hard time figuring the cause
@Oberonc easiest answer is to run the server as normal, whatever you do in production, and attach the debugger to that - typically you just pass an extra jvm arg, but sometimes your IDE has specific integration
if you need to debug gwt at the same time, sdm can run and let you serve its js from any web server that can serve normal js
if you are already using gwt's DevMode process, just starting it with your IDE's debug settings will let you debug the server classes normally, but we generally advise against that