GWT Boot - Better Implementation

YourEntryPoint.java

package hello.client;

import com.google.gwt.core.client.*;
import com.google.gwt.user.client.ui.*;

@GwtModule(renameTo="basic")
public class YourEntryPoint implements EntryPoint {
   @Override
   public void onModuleLoad() {
      Button button = new Button("Click me");
      button.addClickHandler(clickEvent -> { 
         Window.alert("Hello World!"); 
      });
      RootPanel.get("helloButton").add(button);
   }
   
   @GwtModuleProperty
   public String inherits() {
      return "com.github.gwtboot.starter.Starter";  
   } 
   
   @GwtModuleProperty
   public String sourcePath() {
      return "client";
   }
   
   @GwtModuleProperty
   public Map setProperty() {
      Map<String, String> map = new HashMap<>();
      map.add("gwt.logging.logLevel", "INFO");
      map.add("gwt.logging.enabled", "TRUE");
      return map;
   }
}

I think the current design of GWT modules is centered around the whole module, not just the entry point. Sooner or later, J2CL will have to adopt the new Java 9+ modular system. Therefore, a better approach might be to start fresh with Java 9 and J2CL and implement modular annotations as shown in this GWT example module-info.java :

//You can have module-level annotations in Java 9!
@GwtModule(name="MyModule")
@GwtEntryPoint(MyEntryPoint.class) //How many entry points can we have? Errai allows for many

//With repeatable annotations, you can replace <define-property name="..." values="..." />
GwtProperty(name="formfactor",values="desktop,tablet,mobile")
GwtProperty(name="locale",values="en,fr")
module gwtproject.myModule {

   //replacement for  <inherits name=.../>
    requires static gwtproject.otherModule; 
 
   //transitive dependencies
    requires static transitive gwtproject.yetAnotherModule;   
}

notice the use of static - this is typically the case with GWT where the transpiler converts Java->JS, but none of the original code is needed at run-time.

Yes, I agree with you.