If nobody is interested in maintaining such, it could be presented as a
demonstration valid in 2024. I can post my version of it and others can make
revisions or advise.
Sent from Yahoo Mail on Android
On Sun, Feb 25, 2024 at 0:12, Craig Mitchell wrote:
> My question is: what do you expe
> *My question is: what do you expect from such an archetype?*
It would be great to have an example for a minimum viable product. So how
to do a mvn package on an app created
with https://github.com/tbroyer/gwt-maven-archetypes to get an executable
jar that doesn't need an existing web server.
In retrospect, I think the GWT BOM (to avoid managing non-GWT dependencies
where there's no need to) possibly either should only be used in the client
module, or should really only list GWT artifacts. That being said, if you
use the Jetty BOM in the server module (and you should), it should over
The gwt artifact is indeed in dependency management, but when the jetty-main
jar for jetty 11 is a dependency of server module it draws in jetty 9
dependencies and and also gwt-servlet leading to a no javax-servlet error.
Remove gwt from the root fixes it. Maybe this will cause problems beyond
I could easily write a Main class that runs an embedded Jetty server
(https://eclipse.dev/jetty/documentation/jetty-12/programming-guide/index.html#pg-server-http-handler-use-servlet-context)
with the configured GWT-RPC servlet and serving static resources from
multiple dirs
(https://eclipse.d
> *Could try moving the gwt dependency out of the root pom, keeping it
only for the client, just gwt-servlet for sever and shared ( unless anyone
knows better). That will clean up the server dependencies but may cause
other problems *
I believe that's how it works now. The root pom just has t
Could try moving the gwt dependency out of the root pom, keeping it only for
the client, just gwt-servlet for sever and shared ( unless anyone knows
better). That will clean up the server dependencies but may cause other
problems
Sent from Yahoo Mail on Android
On Fri, Feb 23, 2024 at 6:4
Don’t want to build up pressure, but yeah that would come in very handy 😎
Craig Mitchell schrieb am Fr. 23. Feb. 2024 um
00:05:
> I know it's outside of its scope, but it would be great if
> https://github.com/tbroyer/gwt-maven-archetypes had an example of "If you
> want to create an executable
I know it's outside of its scope, but it would be great
if https://github.com/tbroyer/gwt-maven-archetypes had an example of "If
you want to create an executable jar with Jetty, this is how you could do
it". 🙂
On Thursday 22 February 2024 at 5:30:51 am UTC+11 Tim Macpherson wrote:
> I tried s
I tried starting with the tbroyer archetype & to the server project I added the
app engine stuff from the Google sample to build the appengine-staging
dependencies directory.Maybe all that should be in a separate project ?
Sent from Yahoo Mail on Android
On Wed, Feb 21, 2024 at 17:42, Thoma
On Wednesday, February 21, 2024 at 3:11:54 PM UTC+1 tim_mac...@yahoo.co.uk
wrote:
I've been trying this app engine sample for Java 11+ which uses a JAR
packaged artifact that is installed locally:
it provides a Main class to instantiate an HTTP server to run an embedded
web application WAR fi
I've been trying this app engine sample for Java 11+ which uses a JAR packaged
artifact that is installed locally:it provides a Main class to instantiate an
HTTP server to run an embedded web application WAR
file.github.com/GoogleCloudPlatform/java-docs-samples/tree/main/appengine-java11/appeng
Fwiw, I haven't used WARs for years (and by years I mean more than a
decade), but the archetype is only there to help you get started with
cleanly separated client/shared/server modules, and I don't want to impose
my own opinionated way of building apps to others (or possibly start
bikeshedding
Now I have it all working. This is what I found:
Google App Engine Standard no longer gives you a web server, so you need to
provide your own.
- If you use https://github.com/tbroyer/gwt-maven-archetypes you get
Jetty when running in dev, but nothing when doing a mvn package (just a war
Maybe this thread is gettig a bit off-topic for gwt ? maybe more suitable
for Stackoverflow
or
https://groups.google.com/g/google-appengine
& https://groups.google.com/g/google-cloud-dev
now superceded by
https://www.googlecloudcommunity.com/gc/Serverless/bd-p/cloud_serverless.
On Tuesday, Decemb
Odd, my message was deleted. Maybe it was too boring. :-D
The highlights:
- I'm not sure if you get a Jetty server bundled or not if you use the
legacy bundled services. The documentation is a little ambiguous to me.
- You do get a stand alone server "dev server" that you can deploy
Looks like Cloud CLI provides a dev server if using the legacy bundled
services (App Engine API JAR)?
https://cloud.google.com/appengine/docs/standard/java-gen2/services/access
If you are using the legacy bundled services, the second-generation Java
runtimes provide the Jetty web-serving framew
Thanks again Tim!
*> Afaik gwt:devmode is launching a GWT Jetty, rather than the GAE Jetty.>
The latter requires appengine:run*
This is no longer an option. appengine:run no longer works with Java17.
You have to provide your own web server.
See
https://cloud.google.com/appengine/migrati
Afaik gwt:devmode is launching a GWT Jetty, rather than the GAE Jetty.
The latter requires appengine:run
with a launch profile env property & name
appengine:run -Denv=haslistener
As you say: for IDE debugging: we need a Remote Java Application &
jvmFlags, discussed at length here:
https://stack
Managed to get server debugging working by adding:
-Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005
to the gwt-maven-plugin.
And then creating a Remote JVM Debug launcher in IntelliJ (on port 5005),
that I run after running gwt:devmode.
I'm surprised IntelliJ can't just automatica
Thanks Tim! Looking at your POM files, I see I missed adding:
${project.build.directory}/${project.artifactId}-${project.version}/WEB-INF/classes
I also needed to:
- Convert all my servlets to @WebServlet (as the GWT Jetty server didn't
pick up my web.xml like the GAE server used to).
These are my current poms, based on the tbroyer archetype.
Probably best to look at the latter first if youre not familiar with it.
The launch is configured in the server pom:
env-dev-gae1
env
haslistener
...
Forgot to mention. My target is Java 17, but my source is Java 1.8.
So:
1.8
17
And:
org.apache.maven.plugins
maven-compiler-plugin
3.11.0
${maven.compiler.source}
${maven.compiler.target}
org.apache.maven.plugins
maven-resources-plugin
3.3.1
I've attached my current POM (which isn't
Hi Tim,
I thought GWT 2.10.0 supported Java17. From the release notes:
https://www.gwtproject.org/release-notes.html#Release_Notes_2_10_0
*Tested support for running on Java 17, dropped remaining support for
running on Java 7.*
I'm also using appengine-maven-plugin 2.5.0.
com.google.cloud.t
I havent tried raising the Java level yet, its still JavaSE-1.8.
Got as far as using latest versions:
JDK 21
gcloud CLI app & cloudSdkVersion 457.0.0
appengine-maven-plugin 2.5.0
To get it to run, so far:
1 I had to remove all DOCTYPE declarations in xml files in the server
project (new restr
No worries not posting the POMs Tim.
The bit I'm struggling with, the old Java 8 version had its own GAE
server. So I would run that, and a GWT Code Server. Easy!
*btw:* I'm talking about GAE Standard. GAE Flexible you can do whatever
you want, but that's more work and more expensive.
Now w
For some years I've been deploying GWT 2.8.2 to GAE with Maven & Google
Cloud Tools.
I now find GAE is not supporting Java 8 after January, so currently
upgrading (rather slowly).
There are 4 long POM files, probably better to mail them then post a
distilled version here ?
On Sunday, Decembe
Hi,
The instructions
here https://www.gwtproject.org/doc/latest/tutorial/appengine.html are no
longer valid, as the Google Plugin for Eclipse is now dead (Google no
longer supports Java 1.8, and the Google Plugin for Eclipse doesn't support
any Eclipse versions that support anything after Java
28 matches
Mail list logo
