Had a problem trying GWT 2.11.0

[jamal....@gmail.com]

After generating a project skeleton using the latest gwt-maven-archetypes, done the usual:
- mvn gwt:codeserver -pl *-client -am

- mvn jetty:run -pl *-server -am -Denv=dev

The first command executed without problems, however the second one failed to start jetty showing on terminal the following error:

[ERROR] SAX Parse Issue @null line:1 col:59 : org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 59; cvc-elt.1.a: Cannot find the declaration of element 'Configure'.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for gwt-gpt 1.0-SNAPSHOT:
[INFO]
[INFO] gwt-gpt ............................................ SUCCESS [  5.841 s]
[INFO] gwt-gpt-shared ..................................... SUCCESS [  1.400 s]
[INFO] gwt-gpt-server ..................................... FAILURE [  0.703 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  14.168 s
[INFO] Finished at: 2024-02-04T16:51:35Z
[INFO] ------------------------------------------------------------------------

After many searches I found that context.xml in jettyconf folder had missing dtd schema. Adding that as follows jetty started with no error:

<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN" "http://www.eclipse.org/jetty/configure.dtd">

<Configure class="org.eclipse.jetty.webapp.WebAppContext">

<Call name="setInitParameter">

<Arg>org.eclipse.jetty.servlet.Default.useFileMappedBuffer</Arg>

<Arg>false</Arg>

</Call>

</Configure>

[tim_mac...@yahoo.co.uk]

I also found that out eventually.

Another thing: The server module needs /target /jetty_overlays  folder for running env-prod.

[Thomas Broyer]

Just published version 2024.2.5 of the archetypes that adds a DOCTYPE linking to the DTD to the context.xml.

I could reproduce the jetty_overlays error in env=prod, but that really looks like a bug in the jetty-maven-plugin (and creating the directory allows the server to start, but it was still missing the overlay, so no *.nocache.js loaded from the HTML host page).