Friday, January 31, 2020

Re: i18n Failing

<set-property name="locale" value="en,es" />
That fixed it. Thanks.

On Friday, January 31, 2020 at 5:11:28 AM UTC-8, Thomas Broyer wrote:
You'll want to
<set-property name="locale" value="en,es" />

The reason for this set-property is to remove the "default" value from the available values (the locale property is defined with a single "default" initial value, you later extend it to add en and es, so it's now default,en,es, and then you overwrite it with this set-property to just en,es).

Actually, if you support an English locale, you don't really need the remove the "default" value, as it'll be equivalent to "en" (in most cases at least) thus won't produce an additional permutation anyway. To make it work though, you need to put your English translations in the FixedStrings (or other localizable interfaces) annotations and/or in the non-suffixed .properties file (i.e. rename FixedStrings_en.properties to FixedStrings.properties).

On Friday, January 31, 2020 at 10:36:48 AM UTC+1, Andrew Buck wrote:
I am trying to add a second locale to my GWT app, but I'm unable to make it work.

Up until now, I've had:
<extend-property name="locale" values="en" />
<set-property name="locale" value="en" />
<set-property-fallback name="locale" value="en"/>

And now if I change it to:
<extend-property name="locale" values="en,es" />
<set-property name="locale" value="en" />
<set-property-fallback name="locale" value="en"/>

And add a tag in the page header:
<meta name='gwt:property' content='locale=es'/>

I still always see the page in English.

If I instead do:
<extend-property name="locale" values="en,es" />
<set-property name="locale" value="es" />
<set-property-fallback name="locale" value="en"/>

Then I always see the page in Spanish.

The <set-property...> tag is not shown in the GWT documentation, but if I remove it, then I get a compile error: 
"Failed to resolve '[package-name].i18n.FixedStrings' via deferred binding"

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/92a402a6-d15d-46ec-8b3d-699dc7ca1bbd%40googlegroups.com.

Re: i18n Failing

Hi,

For EN and DE I have the following

<!-- Locale -->
<inherits name="com.google.gwt.i18n.I18N" />

<!-- German language, independent of country -->
<extend-property name="locale" values="de" />
<extend-property name='locale' values='de_DE' />
<!-- English language, independent of country -->
<extend-property name="locale" values="en" />
<set-property-fallback name='locale' value='en' />
<set-property name='locale' value='de_DE' />

extend-property - add support for a specific locale, set-property, in the end, sets the "default" locale. 

Best,
Stas

On Friday, January 31, 2020 at 10:36:48 AM UTC+1, Andrew Buck wrote:
I am trying to add a second locale to my GWT app, but I'm unable to make it work.

Up until now, I've had:
<extend-property name="locale" values="en" />
<set-property name="locale" value="en" />
<set-property-fallback name="locale" value="en"/>

And now if I change it to:
<extend-property name="locale" values="en,es" />
<set-property name="locale" value="en" />
<set-property-fallback name="locale" value="en"/>

And add a tag in the page header:
<meta name='gwt:property' content='locale=es'/>

I still always see the page in English.

If I instead do:
<extend-property name="locale" values="en,es" />
<set-property name="locale" value="es" />
<set-property-fallback name="locale" value="en"/>

Then I always see the page in Spanish.

The <set-property...> tag is not shown in the GWT documentation, but if I remove it, then I get a compile error: 
"Failed to resolve '[package-name].i18n.FixedStrings' via deferred binding"

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/4c8d0d55-723d-45e6-92fb-927e511637ce%40googlegroups.com.

Re: i18n Failing

You'll want to
<set-property name="locale" value="en,es" />

The reason for this set-property is to remove the "default" value from the available values (the locale property is defined with a single "default" initial value, you later extend it to add en and es, so it's now default,en,es, and then you overwrite it with this set-property to just en,es).

Actually, if you support an English locale, you don't really need the remove the "default" value, as it'll be equivalent to "en" (in most cases at least) thus won't produce an additional permutation anyway. To make it work though, you need to put your English translations in the FixedStrings (or other localizable interfaces) annotations and/or in the non-suffixed .properties file (i.e. rename FixedStrings_en.properties to FixedStrings.properties).

On Friday, January 31, 2020 at 10:36:48 AM UTC+1, Andrew Buck wrote:
I am trying to add a second locale to my GWT app, but I'm unable to make it work.

Up until now, I've had:
<extend-property name="locale" values="en" />
<set-property name="locale" value="en" />
<set-property-fallback name="locale" value="en"/>

And now if I change it to:
<extend-property name="locale" values="en,es" />
<set-property name="locale" value="en" />
<set-property-fallback name="locale" value="en"/>

And add a tag in the page header:
<meta name='gwt:property' content='locale=es'/>

I still always see the page in English.

If I instead do:
<extend-property name="locale" values="en,es" />
<set-property name="locale" value="es" />
<set-property-fallback name="locale" value="en"/>

Then I always see the page in Spanish.

The <set-property...> tag is not shown in the GWT documentation, but if I remove it, then I get a compile error: 
"Failed to resolve '[package-name].i18n.FixedStrings' via deferred binding"

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/4736124a-85d1-46a4-adab-8bcee2bcf400%40googlegroups.com.

i18n Failing

I am trying to add a second locale to my GWT app, but I'm unable to make it work.

Up until now, I've had:
<extend-property name="locale" values="en" />
<set-property name="locale" value="en" />
<set-property-fallback name="locale" value="en"/>

And now if I change it to:
<extend-property name="locale" values="en,es" />
<set-property name="locale" value="en" />
<set-property-fallback name="locale" value="en"/>

And add a tag in the page header:
<meta name='gwt:property' content='locale=es'/>

I still always see the page in English.

If I instead do:
<extend-property name="locale" values="en,es" />
<set-property name="locale" value="es" />
<set-property-fallback name="locale" value="en"/>

Then I always see the page in Spanish.

The <set-property...> tag is not shown in the GWT documentation, but if I remove it, then I get a compile error: 
"Failed to resolve '[package-name].i18n.FixedStrings' via deferred binding"

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/f1630635-44ba-4039-b1a9-3869005a3558%40googlegroups.com.

Wednesday, January 29, 2020

Re: Maven Plugin for GWT: "An internal error occurred during: "BBj - GWT Compile". Model not available for BBj"

Update: I found a classpath entry that does use Gradle, and the GWT Compile runs when I remove that Gradle-related entry. Now that I've isolated the source of the problem, I'm trying (with no success yet) to work around it. It looks like this is the main bug report:

https://github.com/eclipse/buildship/issues/936

On Tuesday, January 28, 2020 at 9:25:55 AM UTC-8, Jim Douglas wrote:
Still feeling my way around this. It seems clear that there was a bug introduced in Eclipse 2019-09 that still exists in Eclipse 2019-12. This Eclipse bug report shows the same basic error from a different context:


The challenge here is that the package in question doesn't use Gradle at all.

On Monday, January 27, 2020 at 10:39:54 AM UTC-8, Jim Douglas wrote:
Gradle is used in another package in this project, but not in the package where I'm trying to do a GWT Compile; this package doesn't use gradle at all.

I do see reports of this same internal gradle exception in recent Eclipse distributions:



On Saturday, January 25, 2020 at 9:51:32 AM UTC-8, Jens wrote:
Looks like Eclipse wants to resolve classpath entries using Gradle (through Eclipse Buildship Plugin bundled with Eclipse to support project configuration based on Gradle).

Maybe Gradle is enabled in your project for any reason, even though you are using Maven?

-- J.

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/30c500e9-51a0-48f8-994a-251722ab6446%40googlegroups.com.

Tuesday, January 28, 2020

Re: Custom Post Linker and Super Dev Mode

On Tuesday, January 28, 2020 at 4:48:32 AM UTC-5, Thomas Broyer wrote:
Those methods are to be called from the client code, not the linker itself.

Ok -- makes sense. If I modify the client code that makes those requests to use getModuleBaseForStaticFiles(), it looks like it's now trying to load them from the code server port instead -- assume that's expected?  If I log the output of both methods, I can see the ports are different.

Unfortunately, the new base URL doesn't seem to have helped me. Now I see "[WARN] ignored get request: /path/to/file" for the URL and if I make a curl request, I can see that it's coming back with a 200 and content length 0.

So .... it's different, but not totally working either?

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/8f3c1799-877d-4779-b4f7-abbb1f5ca9a1%40googlegroups.com.

Re: Maven Plugin for GWT: "An internal error occurred during: "BBj - GWT Compile". Model not available for BBj"

Still feeling my way around this. It seems clear that there was a bug introduced in Eclipse 2019-09 that still exists in Eclipse 2019-12. This Eclipse bug report shows the same basic error from a different context:


The challenge here is that the package in question doesn't use Gradle at all.

On Monday, January 27, 2020 at 10:39:54 AM UTC-8, Jim Douglas wrote:
Gradle is used in another package in this project, but not in the package where I'm trying to do a GWT Compile; this package doesn't use gradle at all.

I do see reports of this same internal gradle exception in recent Eclipse distributions:



On Saturday, January 25, 2020 at 9:51:32 AM UTC-8, Jens wrote:
Looks like Eclipse wants to resolve classpath entries using Gradle (through Eclipse Buildship Plugin bundled with Eclipse to support project configuration based on Gradle).

Maybe Gradle is enabled in your project for any reason, even though you are using Maven?

-- J.

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/4bdf1ddb-01a7-43ee-834f-5ee2978046bd%40googlegroups.com.

Re: Custom Post Linker and Super Dev Mode



On Monday, January 27, 2020 at 10:39:01 PM UTC+1, Geoffrey Wiseman wrote:
On Wednesday, January 15, 2020 at 3:49:34 AM UTC-5, Thomas Broyer wrote:
IIRC, with Super Dev Mode, public artifacts aren't generated in the launcher dir; you need to build your path relative to GWT.getModuleBaseForStaticFiles() rather than GWT.getModuleBase(). HTH

Cautionary preamble: I wasn't involved in the creation of this linker, and I haven't done much with GWT linkers, so it is entirely possible that I'm missing something here. Having said all that:

The linker that I've seen break down in SuperDevMode just calls `emitString` to create some text resources that are then requested later by the browser. Those resources were visible to dev mode in the past, and they're visible in the built GWT application, but in SuperDevMode, they 404. Near as I can tell, the linker isn't using `getModuleBase` or `getModuleBaseForStaticFiles` at all.

Those methods are to be called from the client code, not the linker itself.
 
But with this response I was able to find another thread:

Sounds like you were saying there that it may not be possible to fix this for SuperDevMode? It definitely *does* work in the final built WAR file, it's only SuperDevMode where this seems to break down. So if I create artifacts using `emitString` in a custom linker, there's no way to have these be accessible in SuperDevMode?

If you emitString() with a partialPath of "foo.txt", then it should be accessible in SDM at GWT.getModuleBaseForStaticFiles() + "foo.txt" (but not GWT.getModuleBaseURL() + "foo.txt"). In production mode, it'll be accessible through both, as getModuleBaseForStaticFiles and getModuleBaseURL return the same value then.
 

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/9fa84541-4581-4247-88ac-88b1cee60389%40googlegroups.com.

Monday, January 27, 2020

Re: Custom Post Linker and Super Dev Mode

On Wednesday, January 15, 2020 at 3:49:34 AM UTC-5, Thomas Broyer wrote:
IIRC, with Super Dev Mode, public artifacts aren't generated in the launcher dir; you need to build your path relative to GWT.getModuleBaseForStaticFiles() rather than GWT.getModuleBase(). HTH

Cautionary preamble: I wasn't involved in the creation of this linker, and I haven't done much with GWT linkers, so it is entirely possible that I'm missing something here. Having said all that:

The linker that I've seen break down in SuperDevMode just calls `emitString` to create some text resources that are then requested later by the browser. Those resources were visible to dev mode in the past, and they're visible in the built GWT application, but in SuperDevMode, they 404. Near as I can tell, the linker isn't using `getModuleBase` or `getModuleBaseForStaticFiles` at all.

But with this response I was able to find another thread:
https://www.mail-archive.com/google-web-toolkit@googlegroups.com/msg105012.html

Sounds like you were saying there that it may not be possible to fix this for SuperDevMode? It definitely *does* work in the final built WAR file, it's only SuperDevMode where this seems to break down. So if I create artifacts using `emitString` in a custom linker, there's no way to have these be accessible in SuperDevMode?



--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/c81f5a6e-b776-4b76-ba54-34e5e4a7f98b%40googlegroups.com.

Re: Maven Plugin for GWT: "An internal error occurred during: "BBj - GWT Compile". Model not available for BBj"

Gradle is used in another package in this project, but not in the package where I'm trying to do a GWT Compile; this package doesn't use gradle at all.

I do see reports of this same internal gradle exception in recent Eclipse distributions:



On Saturday, January 25, 2020 at 9:51:32 AM UTC-8, Jens wrote:
Looks like Eclipse wants to resolve classpath entries using Gradle (through Eclipse Buildship Plugin bundled with Eclipse to support project configuration based on Gradle).

Maybe Gradle is enabled in your project for any reason, even though you are using Maven?

-- J.

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/145e3e40-82da-454b-9696-7d2278e82f89%40googlegroups.com.

Re: Is GWT 3.0 /GWT 2.9 dead?

Atm the community is very active. We are working on GWT modules: replacing generators and JSNI, testig the migraed moules against J2CL, etc.
Besides that, many new frameworks are evolving.

Take a look at this rooms:
https://gitter.im/gwtproject/gwt
to get more infos.

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/a3ae5c60-6dc7-43f0-b3c9-02a6e6d18bf9%40googlegroups.com.

Re: Is GWT 3.0 /GWT 2.9 dead?

You should ask this question here: https://gitter.im/gwtproject/gwt

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/27aad5bc-85d3-41b1-a642-f9d5e0985b58%40googlegroups.com.

Re: GWT SuperDev sourcemaps suddenly not being loaded by Chrome/FireFox/IE/Edge

I think I figured it out. I am using a reverse proxy to front both the website delivering the gwt application and the codeserver. The reason for this is because our application requires SSL and I cannot easily switch it off. I based this reverse proxy on example code DevServer from Thomas Broyer. 

However that example code is not very complete. I noticed that it is still generating a sourceMapping 
URL that points directly to the codeserver on a non SSL port 9876.

I hope I can find a solution to rewrite the generated code to point it to the proper url through the reverse proxy.

Why does codeserver make it so hard to support SSL ? I would be nicer if codeserver at least would give us an option where we could tell it to generate proper urls as a path in our website iso expecting cross site links and ignoring the need for SSL.

Even if I would propose a patch for GWT 2.8.2 to improve the codeserver it would be a waste of my time since we are all waiting for a very long time to get an update on the 2.x release. I can't use non official build at my company.
On 24 Jan 2020, 18:18 +0100, Juan Pablo Gardella <gardellajuanpablo@gmail.com>, wrote:
Did you try if org.realityforge.com.google.gwt release has the same problem?

On Fri, 24 Jan 2020 at 14:12, David Nouls <david.nouls@gmail.com> wrote:
I am using GWT for many years now. My project uses 2.8.2 and we are using SDM for debugging.
For some reason suddenly I can no longer debug my application in any of my browsers on my machine.
I was working up to 2 weeks ago.... and now it no longer works.

I have searched the internet for any hints what might be causing this... but found nothing that helps.

The strange thing is that it works when I connect from another PC to the same server that it works.

When SDM starts it prints that sourcemaps are available... but Chrome never even tries to download them.
In IE11 the button to download sourcemaps is disabled (and the mouseover says that there are no sourcemaps available).

Anybody a clue on what is driving the browser to decide that there are sourcemaps or not ?

What I don't get is that the problem is only on my machine (accessing the same server) and the problem is across all the browsers I have installed on it.

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/5ce2b53e-6c9e-46ec-9e88-8b57da873ef0%40googlegroups.com.

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CA%2BkiFsc2u%2BecGZem3L7Hw6_cRVG21JAp17H%3DBm5XJ%3DJibf%3DVjQ%40mail.gmail.com.

Sunday, January 26, 2020

Is GWT 3.0 /GWT 2.9 dead?

Since last 6-7 months there is almost no progress on milestone for GWT 2.9.is is about 62 %.  Is the community still working on these versions or there in no plan to work on these to support Java 11 + releases?

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/f53b16ec-2580-4118-944d-6a8c2f0ff7be%40googlegroups.com.

Saturday, January 25, 2020

Re: Maven Plugin for GWT: "An internal error occurred during: "BBj - GWT Compile". Model not available for BBj"

Looks like Eclipse wants to resolve classpath entries using Gradle (through Eclipse Buildship Plugin bundled with Eclipse to support project configuration based on Gradle).

Maybe Gradle is enabled in your project for any reason, even though you are using Maven?

-- J.

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/11ba0097-08a0-4b03-8285-53e17956f134%40googlegroups.com.

Re: Maven Plugin for GWT: "An internal error occurred during: "BBj - GWT Compile". Model not available for BBj"

Thanks, Jens; does this help at all? As I mentioned at the beginning of this thread, it was working in Eclipse 2019-06, then started failing with this internal exception in Eclipse 2019-09.

org.eclipse.buildship.core.internal.GradlePluginsRuntimeException: Model not available for BBj
at org.eclipse.buildship.core.internal.workspace.GradleClasspathContainerRuntimeClasspathEntryResolver.resolveRuntimeClasspathEntry(GradleClasspathContainerRuntimeClasspathEntryResolver.java:77)
at org.eclipse.buildship.core.internal.workspace.GradleClasspathContainerRuntimeClasspathEntryResolver.resolveRuntimeClasspathEntry(GradleClasspathContainerRuntimeClasspathEntryResolver.java:66)
at org.eclipse.jdt.internal.launching.RuntimeClasspathEntryResolver.resolveRuntimeClasspathEntry(RuntimeClasspathEntryResolver.java:110)
at org.eclipse.jdt.launching.JavaRuntime.resolveRuntimeClasspathEntry(JavaRuntime.java:1505)
at org.eclipse.jdt.internal.launching.DefaultEntryResolver.resolveRuntimeClasspathEntry(DefaultEntryResolver.java:70)
at org.eclipse.jdt.launching.JavaRuntime.resolveRuntimeClasspathEntry(JavaRuntime.java:1508)
at org.eclipse.jdt.launching.JavaRuntime.resolveRuntimeClasspathEntry(JavaRuntime.java:1444)
at com.google.gwt.eclipse.core.compile.GWTCompileRunner.computeClasspath(GWTCompileRunner.java:156)
at com.google.gwt.eclipse.core.compile.GWTCompileRunner.computeCompilerCommandLine(GWTCompileRunner.java:231)
at com.google.gwt.eclipse.core.compile.GWTCompileRunner.compile(GWTCompileRunner.java:81)
at com.google.gwt.eclipse.core.compile.GWTCompileRunner.compileWithCancellationSupport(GWTCompileRunner.java:126)
at com.google.gwt.eclipse.core.actions.GWTCompileToolbarHandler$1.runInWorkspace(GWTCompileToolbarHandler.java:136)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:42)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

On Saturday, January 25, 2020 at 6:37:48 AM UTC-8, Jens wrote:
What does the Eclipse error log show? Sounds like an Eclipse / some plugin issue and the error log should show some stack trace.

-- J.

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/36fda039-0641-49a4-ad9b-25e6ab30e9ea%40googlegroups.com.

Re: Maven Plugin for GWT: "An internal error occurred during: "BBj - GWT Compile". Model not available for BBj"

What does the Eclipse error log show? Sounds like an Eclipse / some plugin issue and the error log should show some stack trace.

-- J.

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/c0c5f6c5-5241-4f8b-9a19-45c4a0f252ee%40googlegroups.com.

Friday, January 24, 2020

Re: Maven Plugin for GWT: "An internal error occurred during: "BBj - GWT Compile". Model not available for BBj"

I'm getting kind of desperate here; can anyone offer any suggestions about this obscure "Model not available" internal GWT build error? I'm currently using:

* Eclipse 2019-12
* OpenJDK 11.0.6
* GWT 2.8.2
Maven Plugin for GWT

Am I doing anything obviously stupid in this pom.xml?

<project xmlns="http://maven.apache.org/POM/4.0.0"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">

<modelVersion>4.0.0</modelVersion>

<groupId>BBj</groupId>

<artifactId>BBj</artifactId>

<version>19.30-SNAPSHOT</version>

    <packaging>gwt-app</packaging>

<dependencyManagement>

<dependencies>

<dependency>

<groupId>com.google.gwt</groupId> 

<artifactId>gwt</artifactId>

<version>2.8.2</version>

<type>pom</type>

<scope>import</scope>

</dependency>

</dependencies>

</dependencyManagement>

<dependencies>

<dependency>

<groupId>com.google.gwt</groupId>

<artifactId>gwt-user</artifactId>

</dependency>

<dependency>

<groupId>com.google.gwt</groupId>

<artifactId>gwt-dev</artifactId>

<exclusions>

<exclusion>

<groupId>xml-apis</groupId>

<artifactId>xml-apis</artifactId>

</exclusion>

<exclusion>

<groupId>net.sourceforge.htmlunit</groupId>

<artifactId>htmlunit</artifactId>

</exclusion>

</exclusions>

</dependency>

</dependencies>

<build>

<sourceDirectory>src</sourceDirectory>

<resources>

<resource>

<directory>src</directory>

<excludes>

<exclude>**/*.java</exclude>

</excludes>

</resource>

<resource>

<directory>.apt_generated</directory>

<excludes>

<exclude>**/*.java</exclude>

</excludes>

</resource>

</resources>

<plugins>

<plugin>

<artifactId>maven-compiler-plugin</artifactId>

<version>3.8.0</version>

<configuration>

<release>11</release>

</configuration>

</plugin>

<plugin>

<groupId>net.ltgt.gwt.maven</groupId>

<artifactId>gwt-maven-plugin</artifactId>

<version>1.0-rc-10</version>

<extensions>true</extensions>

<configuration>

<moduleName>com.basis.bbj.web.gwt.GWTWebClient</moduleName>

                    <outputDirectory>war/WEB-INF/classes</outputDirectory>

</configuration>

</plugin>

</plugins>

</build>

</project>


On Thursday, October 3, 2019 at 7:51:18 AM UTC-7, Jim Douglas wrote:
Any suggestions?

On Wednesday, September 18, 2019 at 11:26:57 AM UTC-7, Jim Douglas wrote:
(That should have said " after updating to Eclipse 2019-09 today.")

On Wednesday, September 18, 2019 at 11:22:07 AM UTC-7, Jim Douglas wrote:
I was able to get a Java 11 / Eclipse 2019-06 development environment building my GWT project with Maven Plugin for GWT a few months ago, but the GWT compile stopped working after updating to Eclipse 2019-06 today, and the error message doesn't give me much to work with. Any idea what this is trying to tell me?

An internal error occurred during: "BBj - GWT Compile".

Model not available for BBj


GWT-compile.png



Here's the pom.xml file for my BBj package:

<project xmlns="http://maven.apache.org/POM/4.0.0"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">

<modelVersion>4.0.0</modelVersion>

<groupId>BBj</groupId>

<artifactId>BBj</artifactId>

<version>19.20-SNAPSHOT</version>

    <packaging>gwt-app</packaging>

<dependencyManagement>

<dependencies>

<dependency>

<groupId>com.google.gwt</groupId> 

<artifactId>gwt</artifactId>

<version>2.8.2</version>

<type>pom</type>

<scope>import</scope>

</dependency>

</dependencies>

</dependencyManagement>

<dependencies>

<dependency>

<groupId>com.google.gwt</groupId>

<artifactId>gwt-user</artifactId>

</dependency>

<dependency>

<groupId>com.google.gwt</groupId>

<artifactId>gwt-dev</artifactId>

<exclusions>

<exclusion>

<groupId>xml-apis</groupId>

<artifactId>xml-apis</artifactId>

</exclusion>

<exclusion>

<groupId>net.sourceforge.htmlunit</groupId>

<artifactId>htmlunit</artifactId>

</exclusion>

</exclusions>

</dependency>

</dependencies>

<build>

<sourceDirectory>src</sourceDirectory>

<resources>

<resource>

<directory>src</directory>

<excludes>

<exclude>**/*.java</exclude>

</excludes>

</resource>

<resource>

<directory>.apt_generated</directory>

<excludes>

<exclude>**/*.java</exclude>

</excludes>

</resource>

</resources>

<plugins>

<plugin>

<artifactId>maven-compiler-plugin</artifactId>

<version>3.8.0</version>

<configuration>

<release>11</release>

</configuration>

</plugin>

<plugin>

<groupId>net.ltgt.gwt.maven</groupId>

<artifactId>gwt-maven-plugin</artifactId>

<version>1.0-rc-10</version>

<extensions>true</extensions>

<configuration>

<moduleName>com.basis.bbj.web.gwt.GWTWebClient</moduleName>

                    <outputDirectory>war/WEB-INF/classes</outputDirectory>

</configuration>

</plugin>

</plugins>

</build>

</project>

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/40a55fdc-e87b-4a65-a220-53531cf90caf%40googlegroups.com.