Thanks for your reply. I do see CodeServer.class on my gwt-dev-2.9.0.jar on my local repo, so not sure why it isn't finding it. And I'm using mvn version 3.6.3, so not sure why it isn't using the SSL version of the repo url. Used both java 8 and 13 to see if there is any difference but couldn't find any.
On Saturday, May 16, 2020 at 6:06:37 AM UTC-6, Thomas Broyer wrote: > > > > On Saturday, May 16, 2020 at 2:49:06 AM UTC+2, Rogelio Flores wrote: >> >> I tried using the Maven Plugin for GWT ( >> https://tbroyer.github.io/gwt-maven-plugin/) with an existing project >> that I just upgraded to use GWT 2.9.0. >> >> When I try running mvn run:codeserver, I get this: >> >> [DEBUG] Arguments: com.google.gwt.dev.codeserver.CodeServer -workDir >> /Users/rflores/workspace/commonui/client-appmark-admin/target/gwt/codeserver >> -allowMissingSrc -src >> /Users/rflores/workspace/commonui/client-appmark-admin/src/main/java >> com.microfocus.am.Adminui >> >> [WARNING] Error: Could not find or load main class >> com.google.gwt.dev.codeserver.CodeServer >> >> [WARNING] Caused by: java.lang.ClassNotFoundException: >> com.google.gwt.dev.codeserver.CodeServer >> >> [INFO] >> ------------------------------------------------------------------------ >> >> [INFO] BUILD FAILURE >> >> [INFO] >> ------------------------------------------------------------------------ >> >> [INFO] Total time: 4.358 s >> >> [INFO] Finished at: 2020-05-14T17:41:51-06:00 >> >> [INFO] >> ------------------------------------------------------------------------ >> >> [ERROR] Failed to execute goal >> net.ltgt.gwt.maven:gwt-maven-plugin:1.0.0:codeserver (default-cli) on >> project commonui-appmark-admin: GWT exited with status 1 -> [Help 1] >> >> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to >> execute goal net.ltgt.gwt.maven:gwt-maven-plugin:1.0.0:codeserver >> (default-cli) on project commonui-appmark-admin: GWT exited with status 1 >> >> at org.apache.maven.lifecycle.internal.MojoExecutor.execute ( >> MojoExecutor.java:215) >> >> at org.apache.maven.lifecycle.internal.MojoExecutor.execute ( >> MojoExecutor.java:156) >> >> at org.apache.maven.lifecycle.internal.MojoExecutor.execute ( >> MojoExecutor.java:148) >> >> at >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject ( >> LifecycleModuleBuilder.java:117) >> >> at >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject ( >> LifecycleModuleBuilder.java:81) >> >> at >> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build >> >> (SingleThreadedBuilder.java:56) >> >> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute ( >> LifecycleStarter.java:128) >> >> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) >> >> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) >> >> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) >> >> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957) >> >> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289) >> >> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193) >> >> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native >> Method) >> >> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke ( >> NativeMethodAccessorImpl.java:62) >> >> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke ( >> DelegatingMethodAccessorImpl.java:43) >> >> at java.lang.reflect.Method.invoke (Method.java:567) >> >> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced ( >> Launcher.java:282) >> >> at org.codehaus.plexus.classworlds.launcher.Launcher.launch ( >> Launcher.java:225) >> >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode ( >> Launcher.java:406) >> >> at org.codehaus.plexus.classworlds.launcher.Launcher.main ( >> Launcher.java:347) >> >> Caused by: org.apache.maven.plugin.MojoExecutionException: GWT exited >> with status 1 >> >> at net.ltgt.gwt.maven.CommandLine.execute (CommandLine.java:73) >> >> at net.ltgt.gwt.maven.AbstractDevModeMojo.execute ( >> AbstractDevModeMojo.java:272) >> >> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo ( >> DefaultBuildPluginManager.java:137) >> >> at org.apache.maven.lifecycle.internal.MojoExecutor.execute ( >> MojoExecutor.java:210) >> >> at org.apache.maven.lifecycle.internal.MojoExecutor.execute ( >> MojoExecutor.java:156) >> >> at org.apache.maven.lifecycle.internal.MojoExecutor.execute ( >> MojoExecutor.java:148) >> >> at >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject ( >> LifecycleModuleBuilder.java:117) >> >> at >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject ( >> LifecycleModuleBuilder.java:81) >> >> at >> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build >> >> (SingleThreadedBuilder.java:56) >> >> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute ( >> LifecycleStarter.java:128) >> >> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) >> >> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) >> >> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) >> >> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957) >> >> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289) >> >> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193) >> >> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native >> Method) >> >> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke ( >> NativeMethodAccessorImpl.java:62) >> >> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke ( >> DelegatingMethodAccessorImpl.java:43) >> >> at java.lang.reflect.Method.invoke (Method.java:567) >> >> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced ( >> Launcher.java:282) >> >> at org.codehaus.plexus.classworlds.launcher.Launcher.launch ( >> Launcher.java:225) >> >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode ( >> Launcher.java:406) >> >> at org.codehaus.plexus.classworlds.launcher.Launcher.main ( >> Launcher.java:347) >> >> [ERROR] >> >> [ERROR] >> >> [ERROR] For more information about the errors and possible solutions, >> please read the following articles: >> >> [ERROR] [Help 1] >> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException >> >> Does anybody know why? >> > > Check in your > ~/.m2/repository/com/google/gwt/gwt-dev/2.9.0/gwt-dev-2.9.0.jar that it > contains the com/google/gwt/dev/codeserver/CodeServer.class, maybe your JAR > is corrupt. > > >> I then tried to create a brand new project to see if I was missing >> something in my configuration by looking at the project created from the >> archetype. I did this: >> >> $ mvn archetype:generate -DarchetypeGroupId=net.ltgt.gwt.archetypes >> -DarchetypeVersion=1.0.0 -DarchetypeArtifactId=modular-webapp >> >> and I get this Error: >> >> [WARNING] Error reading archetype catalog >> http://repo.maven.apache.org/maven2 >> >> org.apache.maven.wagon.TransferFailedException: Transfer failed for >> http://repo.maven.apache.org/maven2 501 HTTPS Required >> >> > > Which version of Maven are you using? Maven has switched to using > https://repo.maven.apache.org since version 3.2.3 ( > https://github.com/apache/maven/commit/92161918698c55f4c108acb8c6042ad86e705b15), > > released 6 years ago! > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/85da43b8-2d9f-46ed-9a7f-2c0698650735%40googlegroups.com.
