On Saturday, February 19, 2022 at 1:57:16 AM UTC+1 [email protected] wrote:
> Hi Jasper > > I'll be just glad if my current progress saves someone's time. > I progress on step by step basis, so far I succeeded in Eclipse build and > debugging. > > Most of my problems were caused by combination of JDK11+ (namely modules) > + Gradle + Eclipse + Eclipse GWT Plugin. > > Reason: GWT SDK gwt-dev.jar contains lot of classes that must not be > visible to Eclipse compiler, but in fact they are, causing dreaded "The > package org.w3c.dom is accessible from more than one module: <unnamed>, > java.xml" error. > When `gradle build` is issued in command line the gwt-dev.jar from the > maven repository is linked, it contains exactly essential google classes > and nothing more. Thus the build succeeds. > > But when you import such project in Eclipse under JDK11+ (I use JDK17) and > select a GWT SDK there're lots of build errors caused by "The package is > accessible from more than one module" > Can't you somehow disable the module path or put all dependencies in the classpath rather than the module path? https://help.eclipse.org/latest/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Freference%2Fref-properties-build-path.htm&resultof%3D%2522%256a%2570%256d%2573%2522%2520%2522%256a%2570%256d%2522%2520 Alternatively, how about not using the Eclipse GWT Plugin? -- 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/de8dff95-a151-4d79-b416-2f8a3e3bf947n%40googlegroups.com.
