GWT with Gradle is only a couple adhoc tasks away, so no need to change build tool because plugins are lacking.
Back to Maven, the archetype doesn't use the embedded jetty in DevMode, so you need to configure the port in the jetty plugin (there has been an issue on that exact matter a few days ago, go check it out, I had put links to the jetty-maven-plugin docs and a configuration snippet).
You would use codeserverArgs on the root POM to configure the CodeServer port if you'd want to change it.
devmodeArgs is for "mvn gwt:devmode" which you won't use here.
…but as I said above, I'd stay with Gradle and replace the plugin with two adhoc JavaExec tasks for compilation and CodeServer/DevMode, and possibly Gretty for launching a servlet container.
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 firstname.lastname@example.org.
To post to this group, send email to email@example.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.