Re: Running GWT 2.4.0 using JDK 17

['Jim Douglas' via GWT Users]

Apologies for the off-topic question, but is there an estimated timeframe 
for GWT 2.11?

On Wednesday, January 3, 2024 at 8:55:25 AM UTC-8 Colin Alworth wrote:

> (I wrote a longer reply, but Google Groups ate it and never posted it, so 
> apologies for brevity here):
>
> Without more information, it is hard to give a specific answer - are you 
> just hoping to update the Java version and make no changes to the 
> application? It might be that nothing at all needs to be done. If you're 
> using GWT-RPC, you might have no changes to make at all, or you might need 
> an --add-opens jvm arg for a few specific classes (fix to be released in 
> GWT 2.11). 
>
> On the other hand, if you're running the compiler or dev mode on Java 17, 
> other changes are likely needed, due to dependencies that have changed with 
> the Java update.
>
> GWT 2.4.0 was released just over 12 years ago, and was intended to run on 
> Java 6 - even Java 8 will only be ten years old in about two months.
>
> On Wednesday, January 3, 2024 at 8:40:28 AM UTC-6 anjana@gmail.com 
> wrote:
>
>> Hi Team,
>>
>> Due to some business constraints our application is still running on old 
>> GWT.2.4.0 and now we wanted to upgrade java version of our application to 
>> JDK 17.  is it possible to run GWT.2.4.0 on an application which uses JDK 
>> 17? if yes, can you please guide me with the helpful  resources for the 
>> same?
>>
>> Thanks,
>> Anjana
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/37fcdf92-7c46-4290-9493-bcb94dd45b85n%40googlegroups.com.

Re: GWT 2.9.0 TextField clear option in Chrome and IE

['Jim Douglas' via GWT Users]

In our project CSS, we set display:none for the ::ms-clear pseudo element.

https://stackoverflow.com/questions/41900431/disable-ie-11-input-clear-x-button

On Tuesday, June 22, 2021 at 1:03:58 AM UTC-7 Hari wrote:

> Hi All, 
> Recently we have upgraded GWT from 2.1.0 to 2.9.0 with GXT 2.3.1a 
> (Officially unsupported), Most major issues have been fixed, how ever we 
> are having an issue with TextField which is generating an HTML 
> input element with type=text, this field in IE is showing with an cross 
> icon to clear the text, but the same is not happening in chrome,
>
> IE
> ___ 
> |  X |
> ---
>
> how to add clear icon with in the text input field in Chrome? Please let 
> me know for more details required.  
>
> Thanks
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/410ca913-e3a2-476f-a343-b4a6d7574086n%40googlegroups.com.

The GWT Eclipse Plugin stopped working in Eclipse 2021-06

['Jim Douglas' via GWT Users]

I just updated my Eclipse development environment from 2021-03 to 2021-06. 
The installed GWT Eclipse Plugin (which hasn't been updated since 2017) no 
longer shows up in the menu bar, and it logs a bunch of errors. Is anyone 
(Brandon?) still maintaining it?

http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/Download.html

  GWT Eclipse Plugin 3.0.0.201710131939 
com.gwtplugins.eclipse.suite.v3.feature.feature.group GWT Eclipse Plugin


org.osgi.framework.BundleException: Could not resolve module: 
com.gwtplugins.gdt.eclipse.core [3649]
  Unresolved requirement: Require-Bundle: 
com.gwtplugins.gdt.eclipse.platform
-> Bundle-SymbolicName: com.gwtplugins.gdt.eclipse.platform; 
bundle-version="3.0.0.201710131939"; singleton:="true"
   com.gwtplugins.gdt.eclipse.platform [3651]
 No resolution report for the bundle.  Bundle was not resolved 
because of a uses constraint violation.
  org.apache.felix.resolver.reason.ReasonException: Uses constraint 
violation. Unable to resolve resource com.gwtplugins.gdt.eclipse.platform 
[osgi.identity; type="osgi.bundle"; version:Version="3.0.0.201710131939"; 
osgi.identity="com.gwtplugins.gdt.eclipse.platform"; singleton:="true"] 
because it is exposed to package 'javax.servlet' from resources 
javax.servlet [osgi.identity; type="osgi.bundle"; 
version:Version="3.0.0.v201112011016"; osgi.identity="javax.servlet"] and 
jakarta.servlet-api [osgi.identity; type="osgi.bundle"; 
version:Version="4.0.0"; osgi.identity="jakarta.servlet-api"] via two 
dependency chains.

Chain 1:
  com.gwtplugins.gdt.eclipse.platform [osgi.identity; type="osgi.bundle"; 
version:Version="3.0.0.201710131939"; 
osgi.identity="com.gwtplugins.gdt.eclipse.platform"; singleton:="true"]
require: (osgi.wiring.bundle=javax.servlet)
 |
provide: osgi.wiring.bundle: javax.servlet
  javax.servlet [osgi.identity; type="osgi.bundle"; 
version:Version="3.0.0.v201112011016"; osgi.identity="javax.servlet"]

Chain 2:
  com.gwtplugins.gdt.eclipse.platform [osgi.identity; type="osgi.bundle"; 
version:Version="3.0.0.201710131939"; 
osgi.identity="com.gwtplugins.gdt.eclipse.platform"; singleton:="true"]
require: (osgi.wiring.bundle=org.eclipse.jetty.servlet)
 |
provide: osgi.wiring.bundle; bundle-version:Version="10.0.5"; 
osgi.wiring.bundle="org.eclipse.jetty.servlet"
  org.eclipse.jetty.servlet [osgi.identity; type="osgi.bundle"; 
version:Version="10.0.5"; osgi.identity="org.eclipse.jetty.servlet"]
import: 
(&(osgi.wiring.package=javax.servlet)(&(version>=4.0.0)(!(version>=5.0.0
 |
export: osgi.wiring.package: javax.servlet
  jakarta.servlet-api [osgi.identity; type="osgi.bundle"; 
version:Version="4.0.0"; osgi.identity="jakarta.servlet-api"]
at org.eclipse.osgi.container.Module.start(Module.java:463)
at 
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1849)
at 
org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136)
at 
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1842)
at 
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1783)
at 
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1747)
at 
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1669)
at 
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at 
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
at 
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)


-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/da623814-ce28-4e1a-bee9-6e961f47f4b3n%40googlegroups.com.

Re: Conflict between gwt-dev.jar and the Java 11 Module system still exists in GWT 2.9.0.

['Jim Douglas' via GWT Users]

Hi Vassilis,

You'll see an error in the format I mentioned ("The package org.w3c.dom is 
accessible from more than one module: , java.xml") for each time 
your application directly references any class that's included in 
gwt-dev.jar and also exists in the core JDK (e.g. any of the classes that 
you see in my first message at the top of this thread). If you don't happen 
to have used any of those classes, then you won't see these errors.

On Tuesday, May 19, 2020 at 1:33:45 AM UTC-7, Vassilis Virvilis wrote:
>
> Hi,
>
> I am an eclipse user and I am running eclipse with java 11. I am using ant 
> + ivy for building (not Maven) but I am flirting with the idea of Gradle.
>
> I have  GWT Eclipse Plugin 3.0.0.201710131939 
> com.gwtplugins.eclipse.suite.v3.feature.feature.group GWT Eclipse Plugin.
>
> However I have GWT build from git tree. It is not the latest version 
> though. It is like 6 months old. I haven't yet upgraded to 2.9 but I will 
> (try).
>
> I had specifies my git GWT-SDK as the default GWT-SDK and I am using SDM 
> command-line gwt codeserver for compile and debug cycles. It works great 
> for me. I don't use the eclipse debugger and I don't care for the old 
> development mode.
>
> Java 11 does not have several EE classes so I have moved to Jakarta. 
> Another fun story for weird values of fun.
>
> I remember having several issues with the java modularization thingy all 
> over my workspace with non GWT projects also but I don't remember how I 
> solved it.
>
> This how I have it in my project's setup. I don't need to manually trim 
> classes from GWT
>
> [image: image.png]
>
> So it is possible to have eclipse, java 11 and a newish GWT.
>
> Hope that helps.
>
>
>
>
> On Tue, May 19, 2020 at 2:47 AM 'Jim Douglas' via GWT Users <
> google-we...@googlegroups.com > wrote:
>
>> I sincerely appreciate that you're trying to offer advice about this, 
>> Thomas, especially in the middle of the night where you are, but it's hard 
>> to imagine a non-Eclipse user fully understanding what I'm describing here. 
>> Is there nobody who still works on GWT who knows about Eclipse and the GWT 
>> Eclipse Plugin? This is a completely vanilla classpath-based, 
>> non-modulepath, Eclipse project that we've been updating with new versions 
>> of Eclipse, Java, and GWT for a decade. The modulepath conflict is 
>> introduced by the JDK itself, with the modularization of the entire JDK 
>> starting in Java 9. You can find many other people trying to make sense of 
>> this inexplicable error message over the past year or so:
>>
>>
>> https://www.google.com/search?q=%22The+package+org.w3c.dom+is+accessible+from+more+than+one+module%3A+%3Cunnamed%3E%2C+java.xml%22
>>
>> I first ran into this brick wall when I tried to update a Java 11 test 
>> environment from Eclipse 2018-12 to Eclipse 2019-03. I finally isolated the 
>> problem to the fact that GWT bundles several classes that are also 
>> distributed as part of the core JDK. The conflict is that GWT is 
>> classpath-oriented, and the JDK is now modulepath-oriented, and as of 
>> version 2019-03, Eclipse started to enforce the recent rule that a given 
>> class cannot appear in both the modulepath and the classpath. For now, I've 
>> hacked around this by stripping the offending classes from GWT to eliminate 
>> the conflict. All of the classes that I was forced to elmininate exist in 
>> the JDK at least as early as Java 8 (I haven't checked Java 7), so it ought 
>> to be possible for the GWT team to simply drop them from gwt-dev.jar, since 
>> it can count on them existing in the JDK itself.
>>
>> I do recognize that your strong preference is that every application 
>> should now be based on Maven, but ours isn't; it's a traditional 
>> application that just defines the classpath, and rearchitecting our 
>> development environment for a few dozen developers just isn't on the table 
>> anytime soon.
>>
>> On Monday, May 18, 2020 at 4:24:56 PM UTC-7, Thomas Broyer wrote:
>>>
>>> Disclaimer: I'm not an Eclipse user.
>>>
>>> Your problem is that Eclipse flags issues that will only happen if you 
>>> use the modulepath (which I would say, in an IDE, would mean "if the 
>>> project is configured to produce a JPMS module"); using the classpath still 
>>> works. So if Eclipse has a way to say that the project is a JPMS module 
>>> (apparently, there is 
>>> https://www.eclipse.org/community/eclipse_newsletter/2018/june/java9andbeyond.php,

Re: Conflict between gwt-dev.jar and the Java 11 Module system still exists in GWT 2.9.0.

['Jim Douglas' via GWT Users]

I sincerely appreciate that you're trying to offer advice about this, 
Thomas, especially in the middle of the night where you are, but it's hard 
to imagine a non-Eclipse user fully understanding what I'm describing here. 
Is there nobody who still works on GWT who knows about Eclipse and the GWT 
Eclipse Plugin? This is a completely vanilla classpath-based, 
non-modulepath, Eclipse project that we've been updating with new versions 
of Eclipse, Java, and GWT for a decade. The modulepath conflict is 
introduced by the JDK itself, with the modularization of the entire JDK 
starting in Java 9. You can find many other people trying to make sense of 
this inexplicable error message over the past year or so:

https://www.google.com/search?q=%22The+package+org.w3c.dom+is+accessible+from+more+than+one+module%3A+%3Cunnamed%3E%2C+java.xml%22

I first ran into this brick wall when I tried to update a Java 11 test 
environment from Eclipse 2018-12 to Eclipse 2019-03. I finally isolated the 
problem to the fact that GWT bundles several classes that are also 
distributed as part of the core JDK. The conflict is that GWT is 
classpath-oriented, and the JDK is now modulepath-oriented, and as of 
version 2019-03, Eclipse started to enforce the recent rule that a given 
class cannot appear in both the modulepath and the classpath. For now, I've 
hacked around this by stripping the offending classes from GWT to eliminate 
the conflict. All of the classes that I was forced to elmininate exist in 
the JDK at least as early as Java 8 (I haven't checked Java 7), so it ought 
to be possible for the GWT team to simply drop them from gwt-dev.jar, since 
it can count on them existing in the JDK itself.

I do recognize that your strong preference is that every application should 
now be based on Maven, but ours isn't; it's a traditional application that 
just defines the classpath, and rearchitecting our development environment 
for a few dozen developers just isn't on the table anytime soon.

On Monday, May 18, 2020 at 4:24:56 PM UTC-7, Thomas Broyer wrote:
>
> Disclaimer: I'm not an Eclipse user.
>
> Your problem is that Eclipse flags issues that will only happen if you use 
> the modulepath (which I would say, in an IDE, would mean "if the project is 
> configured to produce a JPMS module"); using the classpath still works. So 
> if Eclipse has a way to say that the project is a JPMS module (apparently, 
> there is 
> https://www.eclipse.org/community/eclipse_newsletter/2018/june/java9andbeyond.php,
>  
> but things might have changed since then), then disable it and (hopefully) 
> it would solve your issues.
>
> And if you ask me, we should have stopped shipping those ZIP distributions 
> years ago. If you commit your dependencies to your SCM (or anywhere else), 
> then add GWT there as well, downloading the JARs (along with their 
> dependencies) from the Central Repository (use Coursier 
> https://get-coursier.io/, Maven or Ivy to help you with this). I have no 
> idea whether and how the GWT Eclipse Plugin allows you to work with that 
> kind of setup though.
>
> On Monday, May 18, 2020 at 7:59:11 PM UTC+2, Jim Douglas wrote:
>>
>> You lost me there, Thomas. I'm not trying to directly interact with 
>> gwt-dev.jar; I'm just pointing Eclipse to a GWT SDK, the same way I've been 
>> doing for years. Are you saying that standard GWT SDKs are now considered 
>> to be incompatible with Eclipse? If that's the situation, is it documented 
>> anywhere, and is there an official download for Eclipse-compatible GWT SDKs 
>> that I can plugin to that Eclipse dialogue?
>>
>> On Monday, May 18, 2020 at 10:42:42 AM UTC-7, Thomas Broyer wrote:
>>>
>>> The gwt-dev.jar from the ZIP distribution is an uber-jar with all 
>>> dependencies needed to run GWT (so you only need gwt-dev.jar and 
>>> gwt-user.jar in your classpath, and any third-party dependency you're 
>>> using), so this is expected.
>>> Use gwt-dev from the Central Repository (aka Maven Central) instead, 
>>> which bundles only Eclipse ECJ and declares dependencies on the rest.
>>>
>>> On Monday, May 18, 2020 at 7:18:34 PM UTC+2, Jim Douglas wrote:

 I struggled with a module-related issue a year ago when I tried to 
 configure an Eclipse 2019-03 + Java 11 build environment with a project 
 that includes GWT 2.8.2. These are my testing notes from the time:

 Updating a working Java 11 build environment from Eclipse 2018-12 to 
 2019-03 introduced several thousand build errors in the format "The 
 package 
 org.w3c.dom is accessible from more than one module: , java.xml". 
 Apparently these errors are all caused by a project importing a package 
 via 
 the traditional classpath that also exists in the JDK's modulepath. The 
 error message is maddeningly vague; it gives no clue where it sees a 
 conflict (i.e. some particular imported jar file). After resolving all 
 obvious conflicts, I made a copy of my gwt-2.8.2 directory

Re: Conflict between gwt-dev.jar and the Java 11 Module system still exists in GWT 2.9.0.

['Jim Douglas' via GWT Users]

What exception?

If you're seeing error messages in the general format "The package 
org.w3c.dom is accessible from more than one module: , java.xml" 
when you build your GWT project with Java 11, then it's the same issue I 
described here.

On Monday, May 18, 2020 at 1:53:49 PM UTC-7, Dr. Lofi Dewanto wrote:
>
> I have general the problem: Using OpenJDK 11 with my latest Eclipse 
> 2020-03. It always gives me an exception, so that I could not use JDK 11 
> with my latest Eclipse.
>
> Therefore I still use JDK 8 to run my Eclipse 2020-03... I haven't got any 
> time to search why...
>
> Thanks,
> Lofi
>
> Am Montag, 18. Mai 2020 19:18:34 UTC+2 schrieb Jim Douglas:
>>
>> I struggled with a module-related issue a year ago when I tried to 
>> configure an Eclipse 2019-03 + Java 11 build environment with a project 
>> that includes GWT 2.8.2. These are my testing notes from the time:
>>
>> Updating a working Java 11 build environment from Eclipse 2018-12 to 
>> 2019-03 introduced several thousand build errors in the format "The package 
>> org.w3c.dom is accessible from more than one module: , java.xml". 
>> Apparently these errors are all caused by a project importing a package via 
>> the traditional classpath that also exists in the JDK's modulepath. The 
>> error message is maddeningly vague; it gives no clue where it sees a 
>> conflict (i.e. some particular imported jar file). After resolving all 
>> obvious conflicts, I made a copy of my gwt-2.8.2 directory and hacked the 
>> gwt-dev.jar file to remove the packages that I see referenced in these 
>> error messages (netscape.javascript.*, javax.xml.*, org.xml.*, and 
>> org.w3c.*):
>>
>> scrappy:gwt-2.8.2-mod jimdouglas$ zip -d gwt-dev.jar "org/w3c/*" 
>> "org/xml/*" "javax/xml/*" "netscape/javascript/*"
>>
>> My initial testing of GWT 2.9.0 looks pretty good; it appears to just 
>> drop in and work with no issues whatsoever in an Eclipse Java 8 development 
>> environment. But I do still see these module conflicts in my Eclipse 
>> 2020-03 + AdoptOpenJDK 11.0.7 development environment. In limited testing, 
>> that same hack to gwt-dev.jar seems to resolve all of those conflicts:
>>
>> scrappy:gwt-2.9.0-mod jimdouglas$ zip -d gwt-dev.jar "org/w3c/*" 
>> "org/xml/*" "javax/xml/*" "netscape/javascript/*"
>>
>> deleting: javax/xml/
>>
>> deleting: javax/xml/datatype/
>>
>> deleting: javax/xml/namespace/
>>
>> deleting: javax/xml/parsers/
>>
>> deleting: javax/xml/stream/
>>
>> deleting: javax/xml/stream/events/
>>
>> deleting: javax/xml/stream/util/
>>
>> deleting: javax/xml/transform/
>>
>> deleting: javax/xml/transform/dom/
>>
>> deleting: javax/xml/transform/sax/
>>
>> deleting: javax/xml/transform/stax/
>>
>> deleting: javax/xml/transform/stream/
>>
>> deleting: javax/xml/validation/
>>
>> deleting: javax/xml/ws/
>>
>> deleting: javax/xml/xpath/
>>
>> deleting: netscape/javascript/
>>
>> deleting: org/w3c/
>>
>> deleting: org/w3c/css/
>>
>> deleting: org/w3c/css/sac/
>>
>> deleting: org/w3c/css/sac/helpers/
>>
>> deleting: org/w3c/dom/
>>
>> deleting: org/w3c/dom/bootstrap/
>>
>> deleting: org/w3c/dom/css/
>>
>> deleting: org/w3c/dom/events/
>>
>> deleting: org/w3c/dom/html/
>>
>> deleting: org/w3c/dom/ls/
>>
>> deleting: org/w3c/dom/ranges/
>>
>> deleting: org/w3c/dom/stylesheets/
>>
>> deleting: org/w3c/dom/traversal/
>>
>> deleting: org/w3c/dom/views/
>>
>> deleting: org/w3c/dom/xpath/
>>
>> deleting: org/xml/
>>
>> deleting: org/xml/sax/
>>
>> deleting: org/xml/sax/ext/
>>
>> deleting: org/xml/sax/helpers/
>>
>> deleting: javax/xml/XMLConstants.class
>>
>> deleting: javax/xml/datatype/DatatypeConfigurationException.class
>>
>> deleting: javax/xml/datatype/DatatypeConstants$1.class
>>
>> deleting: javax/xml/datatype/DatatypeConstants$Field.class
>>
>> deleting: javax/xml/datatype/DatatypeConstants.class
>>
>> deleting: javax/xml/datatype/DatatypeFactory.class
>>
>> deleting: javax/xml/datatype/Duration.class
>>
>> deleting: javax/xml/datatype/FactoryFinder$ConfigurationError.class
>>
>> deleting: javax/xml/datatype/FactoryFinder.class
>>
>> deleting: javax/xml/datatype/SecuritySupport$1.class
>>
>> deleting: javax/xml/datatype/SecuritySupport$2.class
>>
>> deleting: javax/xml/datatype/SecuritySupport$3.class
>>
>> deleting: javax/xml/datatype/SecuritySupport$4.class
>>
>> deleting: javax/xml/datatype/SecuritySupport$5.class
>>
>> deleting: javax/xml/datatype/SecuritySupport.class
>>
>> deleting: javax/xml/datatype/XMLGregorianCalendar.class
>>
>> deleting: javax/xml/namespace/NamespaceContext.class
>>
>> deleting: javax/xml/namespace/QName$1.class
>>
>> deleting: javax/xml/namespace/QName.class
>>
>> deleting: javax/xml/parsers/DocumentBuilder.class
>>
>> deleting: javax/xml/parsers/DocumentBuilderFactory.class
>>
>> deleting: javax/xml/parsers/FactoryConfigurationError.class
>>
>> deleting: javax/xml/parsers/FactoryFinder$ConfigurationError.class
>>
>> deleting: javax/xml/parsers/FactoryFinder.class
>>
>> deleting: javax/xml/parsers/FilePathToURI.cl

Re: Conflict between gwt-dev.jar and the Java 11 Module system still exists in GWT 2.9.0.

['Jim Douglas' via GWT Users]

You lost me there, Thomas. I'm not trying to directly interact with 
gwt-dev.jar; I'm just pointing Eclipse to a GWT SDK, the same way I've been 
doing for years. Are you saying that standard GWT SDKs are now considered 
to be incompatible with Eclipse? If that's the situation, is it documented 
anywhere, and is there an official download for Eclipse-compatible GWT SDKs 
that I can plugin to that Eclipse dialogue?

On Monday, May 18, 2020 at 10:42:42 AM UTC-7, Thomas Broyer wrote:
>
> The gwt-dev.jar from the ZIP distribution is an uber-jar with all 
> dependencies needed to run GWT (so you only need gwt-dev.jar and 
> gwt-user.jar in your classpath, and any third-party dependency you're 
> using), so this is expected.
> Use gwt-dev from the Central Repository (aka Maven Central) instead, which 
> bundles only Eclipse ECJ and declares dependencies on the rest.
>
> On Monday, May 18, 2020 at 7:18:34 PM UTC+2, Jim Douglas wrote:
>>
>> I struggled with a module-related issue a year ago when I tried to 
>> configure an Eclipse 2019-03 + Java 11 build environment with a project 
>> that includes GWT 2.8.2. These are my testing notes from the time:
>>
>> Updating a working Java 11 build environment from Eclipse 2018-12 to 
>> 2019-03 introduced several thousand build errors in the format "The package 
>> org.w3c.dom is accessible from more than one module: , java.xml". 
>> Apparently these errors are all caused by a project importing a package via 
>> the traditional classpath that also exists in the JDK's modulepath. The 
>> error message is maddeningly vague; it gives no clue where it sees a 
>> conflict (i.e. some particular imported jar file). After resolving all 
>> obvious conflicts, I made a copy of my gwt-2.8.2 directory and hacked the 
>> gwt-dev.jar file to remove the packages that I see referenced in these 
>> error messages (netscape.javascript.*, javax.xml.*, org.xml.*, and 
>> org.w3c.*):
>>
>> scrappy:gwt-2.8.2-mod jimdouglas$ zip -d gwt-dev.jar "org/w3c/*" 
>> "org/xml/*" "javax/xml/*" "netscape/javascript/*"
>>
>> My initial testing of GWT 2.9.0 looks pretty good; it appears to just 
>> drop in and work with no issues whatsoever in an Eclipse Java 8 development 
>> environment. But I do still see these module conflicts in my Eclipse 
>> 2020-03 + AdoptOpenJDK 11.0.7 development environment. In limited testing, 
>> that same hack to gwt-dev.jar seems to resolve all of those conflicts:
>>
>> scrappy:gwt-2.9.0-mod jimdouglas$ zip -d gwt-dev.jar "org/w3c/*" 
>> "org/xml/*" "javax/xml/*" "netscape/javascript/*"
>>
>> deleting: javax/xml/
>>
>> deleting: javax/xml/datatype/
>>
>> deleting: javax/xml/namespace/
>>
>> deleting: javax/xml/parsers/
>>
>> deleting: javax/xml/stream/
>>
>> deleting: javax/xml/stream/events/
>>
>> deleting: javax/xml/stream/util/
>>
>> deleting: javax/xml/transform/
>>
>> deleting: javax/xml/transform/dom/
>>
>> deleting: javax/xml/transform/sax/
>>
>> deleting: javax/xml/transform/stax/
>>
>> deleting: javax/xml/transform/stream/
>>
>> deleting: javax/xml/validation/
>>
>> deleting: javax/xml/ws/
>>
>> deleting: javax/xml/xpath/
>>
>> deleting: netscape/javascript/
>>
>> deleting: org/w3c/
>>
>> deleting: org/w3c/css/
>>
>> deleting: org/w3c/css/sac/
>>
>> deleting: org/w3c/css/sac/helpers/
>>
>> deleting: org/w3c/dom/
>>
>> deleting: org/w3c/dom/bootstrap/
>>
>> deleting: org/w3c/dom/css/
>>
>> deleting: org/w3c/dom/events/
>>
>> deleting: org/w3c/dom/html/
>>
>> deleting: org/w3c/dom/ls/
>>
>> deleting: org/w3c/dom/ranges/
>>
>> deleting: org/w3c/dom/stylesheets/
>>
>> deleting: org/w3c/dom/traversal/
>>
>> deleting: org/w3c/dom/views/
>>
>> deleting: org/w3c/dom/xpath/
>>
>> deleting: org/xml/
>>
>> deleting: org/xml/sax/
>>
>> deleting: org/xml/sax/ext/
>>
>> deleting: org/xml/sax/helpers/
>>
>> deleting: javax/xml/XMLConstants.class
>>
>> deleting: javax/xml/datatype/DatatypeConfigurationException.class
>>
>> deleting: javax/xml/datatype/DatatypeConstants$1.class
>>
>> deleting: javax/xml/datatype/DatatypeConstants$Field.class
>>
>> deleting: javax/xml/datatype/DatatypeConstants.class
>>
>> deleting: javax/xml/datatype/DatatypeFactory.class
>>
>> deleting: javax/xml/datatype/Duration.class
>>
>> deleting: javax/xml/datatype/FactoryFinder$ConfigurationError.class
>>
>> deleting: javax/xml/datatype/FactoryFinder.class
>>
>> deleting: javax/xml/datatype/SecuritySupport$1.class
>>
>> deleting: javax/xml/datatype/SecuritySupport$2.class
>>
>> deleting: javax/xml/datatype/SecuritySupport$3.class
>>
>> deleting: javax/xml/datatype/SecuritySupport$4.class
>>
>> deleting: javax/xml/datatype/SecuritySupport$5.class
>>
>> deleting: javax/xml/datatype/SecuritySupport.class
>>
>> deleting: javax/xml/datatype/XMLGregorianCalendar.class
>>
>> deleting: javax/xml/namespace/NamespaceContext.class
>>
>> deleting: javax/xml/namespace/QName$1.class
>>
>> deleting: javax/xml/namespace/QName.class
>>
>> deleting: javax/xml/parsers/DocumentBuilder.class
>>
>> deleting: javax/xml/parsers/Docu

Conflict between gwt-dev.jar and the Java 11 Module system still exists in GWT 2.9.0.

['Jim Douglas' via GWT Users]

I struggled with a module-related issue a year ago when I tried to 
configure an Eclipse 2019-03 + Java 11 build environment with a project 
that includes GWT 2.8.2. These are my testing notes from the time:

Updating a working Java 11 build environment from Eclipse 2018-12 to 
2019-03 introduced several thousand build errors in the format "The package 
org.w3c.dom is accessible from more than one module: , java.xml". 
Apparently these errors are all caused by a project importing a package via 
the traditional classpath that also exists in the JDK's modulepath. The 
error message is maddeningly vague; it gives no clue where it sees a 
conflict (i.e. some particular imported jar file). After resolving all 
obvious conflicts, I made a copy of my gwt-2.8.2 directory and hacked the 
gwt-dev.jar file to remove the packages that I see referenced in these 
error messages (netscape.javascript.*, javax.xml.*, org.xml.*, and 
org.w3c.*):

scrappy:gwt-2.8.2-mod jimdouglas$ zip -d gwt-dev.jar "org/w3c/*" 
"org/xml/*" "javax/xml/*" "netscape/javascript/*"

My initial testing of GWT 2.9.0 looks pretty good; it appears to just drop 
in and work with no issues whatsoever in an Eclipse Java 8 development 
environment. But I do still see these module conflicts in my Eclipse 
2020-03 + AdoptOpenJDK 11.0.7 development environment. In limited testing, 
that same hack to gwt-dev.jar seems to resolve all of those conflicts:

scrappy:gwt-2.9.0-mod jimdouglas$ zip -d gwt-dev.jar "org/w3c/*" 
"org/xml/*" "javax/xml/*" "netscape/javascript/*"

deleting: javax/xml/

deleting: javax/xml/datatype/

deleting: javax/xml/namespace/

deleting: javax/xml/parsers/

deleting: javax/xml/stream/

deleting: javax/xml/stream/events/

deleting: javax/xml/stream/util/

deleting: javax/xml/transform/

deleting: javax/xml/transform/dom/

deleting: javax/xml/transform/sax/

deleting: javax/xml/transform/stax/

deleting: javax/xml/transform/stream/

deleting: javax/xml/validation/

deleting: javax/xml/ws/

deleting: javax/xml/xpath/

deleting: netscape/javascript/

deleting: org/w3c/

deleting: org/w3c/css/

deleting: org/w3c/css/sac/

deleting: org/w3c/css/sac/helpers/

deleting: org/w3c/dom/

deleting: org/w3c/dom/bootstrap/

deleting: org/w3c/dom/css/

deleting: org/w3c/dom/events/

deleting: org/w3c/dom/html/

deleting: org/w3c/dom/ls/

deleting: org/w3c/dom/ranges/

deleting: org/w3c/dom/stylesheets/

deleting: org/w3c/dom/traversal/

deleting: org/w3c/dom/views/

deleting: org/w3c/dom/xpath/

deleting: org/xml/

deleting: org/xml/sax/

deleting: org/xml/sax/ext/

deleting: org/xml/sax/helpers/

deleting: javax/xml/XMLConstants.class

deleting: javax/xml/datatype/DatatypeConfigurationException.class

deleting: javax/xml/datatype/DatatypeConstants$1.class

deleting: javax/xml/datatype/DatatypeConstants$Field.class

deleting: javax/xml/datatype/DatatypeConstants.class

deleting: javax/xml/datatype/DatatypeFactory.class

deleting: javax/xml/datatype/Duration.class

deleting: javax/xml/datatype/FactoryFinder$ConfigurationError.class

deleting: javax/xml/datatype/FactoryFinder.class

deleting: javax/xml/datatype/SecuritySupport$1.class

deleting: javax/xml/datatype/SecuritySupport$2.class

deleting: javax/xml/datatype/SecuritySupport$3.class

deleting: javax/xml/datatype/SecuritySupport$4.class

deleting: javax/xml/datatype/SecuritySupport$5.class

deleting: javax/xml/datatype/SecuritySupport.class

deleting: javax/xml/datatype/XMLGregorianCalendar.class

deleting: javax/xml/namespace/NamespaceContext.class

deleting: javax/xml/namespace/QName$1.class

deleting: javax/xml/namespace/QName.class

deleting: javax/xml/parsers/DocumentBuilder.class

deleting: javax/xml/parsers/DocumentBuilderFactory.class

deleting: javax/xml/parsers/FactoryConfigurationError.class

deleting: javax/xml/parsers/FactoryFinder$ConfigurationError.class

deleting: javax/xml/parsers/FactoryFinder.class

deleting: javax/xml/parsers/FilePathToURI.class

deleting: javax/xml/parsers/ParserConfigurationException.class

deleting: javax/xml/parsers/SAXParser.class

deleting: javax/xml/parsers/SAXParserFactory.class

deleting: javax/xml/parsers/SecuritySupport$1.class

deleting: javax/xml/parsers/SecuritySupport$2.class

deleting: javax/xml/parsers/SecuritySupport$3.class

deleting: javax/xml/parsers/SecuritySupport$4.class

deleting: javax/xml/parsers/SecuritySupport$5.class

deleting: javax/xml/parsers/SecuritySupport.class

deleting: javax/xml/stream/EventFilter.class

deleting: javax/xml/stream/FactoryConfigurationError.class

deleting: javax/xml/stream/FactoryFinder$ConfigurationError.class

deleting: javax/xml/stream/FactoryFinder.class

deleting: javax/xml/stream/Location.class

deleting: javax/xml/stream/SecuritySupport$1.class

deleting: javax/xml/stream/SecuritySupport$2.class

deleting: javax/xml/stream/SecuritySupport$3.class

deleting: javax/xml/stream/SecuritySupport$4.class

deleting: javax/xml/stream/SecuritySupport$5.class

deleting: javax/xml/stream/SecuritySupport.clas

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

['Jim Douglas' via GWT Users]

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:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=550966
>
> 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:
>>
>> https://github.com/eclipse/buildship/issues/943
>>
>> https://github.com/microsoft/vscode-java-debug/issues/681
>>
>> 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+unsubscr...@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.

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

['Jim Douglas' via GWT Users]

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:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=550966

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:
>
> https://github.com/eclipse/buildship/issues/943
>
> https://github.com/microsoft/vscode-java-debug/issues/681
>
> 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+unsubscr...@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: Maven Plugin for GWT: "An internal error occurred during: "BBj - GWT Compile". Model not available for BBj"

['Jim Douglas' via GWT Users]

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:

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

https://github.com/microsoft/vscode-java-debug/issues/681

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+unsubscr...@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 it possible to use the new Clipboard API in a GWT app? It depends on document.hasFocus being true.

['Jim Douglas' via GWT Users]

Oh wow, I completely missed that. Of course *navigator* is really 
*window.navigator*. JavaScript sample code almost always references 
*navigator*, not *window.navigator*, and I rarely think of that detail. 
Even after staring at that code for hours looking for something I might 
have missed, that never occurred to me. Thanks, Thomas; that's exactly what 
I was missing. With that simple change, this now works.

On Wednesday, October 16, 2019 at 5:44:05 AM UTC-7, Thomas Broyer wrote:
>
> Have you tried with $wnd.navigator.clipboard?
>
> On Tuesday, October 15, 2019 at 10:40:04 PM UTC+2, Jim Douglas wrote:
>>
>> Ok, there are a few moving parts to this. Keeping it as short as 
>> possible, this is the new Clipboard API:
>>
>> https://developer.mozilla.org/en-US/docs/Web/API/Clipboard
>>
>> Support is extremely limited at the moment, but for now I'd be happy to 
>> get something working in Chrome:
>>
>> https://caniuse.com/#feat=mdn-api_clipboard
>>
>> Here's Google's live sample page:
>>
>> https://googlechrome.github.io/samples/async-clipboard/index.html
>>
>> For obvious reasons, there's a lot of paranoid security around JavaScript 
>> access to the clipboard. This is the specific detail I'm running into:
>>
>>
>> https://stackoverflow.com/questions/56306153/domexception-on-calling-navigator-clipboard-readtext
>>
>> These APIs throw a security exception if document.hasFocus() is false. 
>> And I'm not seeing any way to honour that rule in a GWT app. In my 
>> production app, and in a tiny standalone GWT app I just generated for 
>> testing purposes, document.hasFocus() is always false ($doc.hasFocus() is 
>> true).
>>
>> For testing purposes, I generated the GWT StockWatcher demo app:
>>
>> http://www.gwtproject.org/doc/latest/tutorial/create.html
>>
>> Then I added some UI hooks for clipboard testing elements in 
>> StockWatcher.html:
>>
>> Web Application Starter Project
>>
>>
>> 
>>
>>   
>>
>> Please enter your 
>> name:
>>
>>   
>>
>>   
>>
>> 
>>
>> 
>>
>>   
>>
>>   
>>
>> > >
>>
>>   
>>
>>   
>>
>> 
>>
>> 
>>
>> 
>>
>>   
>>
>> 
>>
>> 
>>
>>   
>>
>> 
>>
>> And minimal testing UI in StockWatcher.java onModuleLoad:
>>
>> TextBox readText = *new* TextBox();
>>
>> readText.setText("readText");
>>
>> Button readTextButton = *new* Button("readText");
>>
>>
>> TextBox writeText = *new* TextBox();
>>
>> writeText.setText("writeText");
>>
>> Button writeTextButton = *new* Button("writeText");
>>
>> 
>>
>> RootPanel.*get*("readTextField").add(readText);
>>
>> RootPanel.*get*("readTextButton").add(readTextButton);
>>
>> 
>>
>> RootPanel.*get*("writeTextField").add(writeText);
>>
>> RootPanel.*get*("writeTextButton").add(writeTextButton);
>>
>> readTextButton.addClickHandler(*new* ClickHandler()
>>
>> {
>>
>> *public* *void* onClick(ClickEvent event)
>>
>> {
>>
>> readText();
>>
>> }
>>
>> });
>>
>> 
>>
>> writeTextButton.addClickHandler(*new* ClickHandler()
>>
>> {
>>
>> *public* *void* onClick(ClickEvent event)
>>
>> {
>>
>> writeText(writeText.getText());
>>
>> }
>>
>> });
>>
>> And corresponding JSNI functions to attempt to invoke the Clipboard API:
>>
>>
>>
>> *public* *native* *void* readText()
>>
>> /*-{
>>
>> try
>>
>> {
>>
>> if (navigator.clipboard)
>>
>> {
>>
>> console.log('navigator.clipboard.readText()');
>>
>> console.log('document.hasFocus()='+document.hasFocus());
>>
>> console.log('$doc.hasFocus()='+$doc.hasFocus());
>>
>> var promise = navigator.clipboard.readText();
>>
>> var resolve = function(text) {
>>
>> console.log(text);
>>
>> };
>>
>> var reject = function(reason) {
>>
>> console.log('navigator.clipboard.readText failed: '
>> +reason);
>>
>> };
>>
>> promise["catch"](reject);
>>
>> promise.then(resolve,reject)["catch"](reject);
>>
>> }
>>
>> else
>>
>> {
>>
>> console.log('This browser does not support 
>> navigator.clipboard.');
>>
>> }
>>
>> }
>>
>> catch (e)
>>
>> {
>>
>> console.error(e,e.stack);
>>
>> }
>>
>> }-*/;
>>
>> 
>>
>>
>> *public* *native* *void* writeText(String p_text)
>>
>> /*-{
>>
>> try
>>
>> {
>>
>> var _this = this;
>>
>> if (navigator.clipboard)
>>
>> {
>>
>> console.log('navigator.clipboard.writeText()');
>>
>> console.log('do

Is it possible to use the new Clipboard API in a GWT app? It depends on document.hasFocus being true.

['Jim Douglas' via GWT Users]

Ok, there are a few moving parts to this. Keeping it as short as possible, 
this is the new Clipboard API:

https://developer.mozilla.org/en-US/docs/Web/API/Clipboard

Support is extremely limited at the moment, but for now I'd be happy to get 
something working in Chrome:

https://caniuse.com/#feat=mdn-api_clipboard

Here's Google's live sample page:

https://googlechrome.github.io/samples/async-clipboard/index.html

For obvious reasons, there's a lot of paranoid security around JavaScript 
access to the clipboard. This is the specific detail I'm running into:

https://stackoverflow.com/questions/56306153/domexception-on-calling-navigator-clipboard-readtext

These APIs throw a security exception if document.hasFocus() is false. And 
I'm not seeing any way to honour that rule in a GWT app. In my production 
app, and in a tiny standalone GWT app I just generated for testing 
purposes, document.hasFocus() is always false ($doc.hasFocus() is true).

For testing purposes, I generated the GWT StockWatcher demo app:

http://www.gwtproject.org/doc/latest/tutorial/create.html

Then I added some UI hooks for clipboard testing elements in 
StockWatcher.html:

Web Application Starter Project




  

Please enter your 
name:

  

  





  

  



  

  







  





  



And minimal testing UI in StockWatcher.java onModuleLoad:

TextBox readText = *new* TextBox();

readText.setText("readText");

Button readTextButton = *new* Button("readText");


TextBox writeText = *new* TextBox();

writeText.setText("writeText");

Button writeTextButton = *new* Button("writeText");



RootPanel.*get*("readTextField").add(readText);

RootPanel.*get*("readTextButton").add(readTextButton);



RootPanel.*get*("writeTextField").add(writeText);

RootPanel.*get*("writeTextButton").add(writeTextButton);

readTextButton.addClickHandler(*new* ClickHandler()

{

*public* *void* onClick(ClickEvent event)

{

readText();

}

});



writeTextButton.addClickHandler(*new* ClickHandler()

{

*public* *void* onClick(ClickEvent event)

{

writeText(writeText.getText());

}

});

And corresponding JSNI functions to attempt to invoke the Clipboard API:

   

*public* *native* *void* readText()

/*-{

try

{

if (navigator.clipboard)

{

console.log('navigator.clipboard.readText()');

console.log('document.hasFocus()='+document.hasFocus());

console.log('$doc.hasFocus()='+$doc.hasFocus());

var promise = navigator.clipboard.readText();

var resolve = function(text) {

console.log(text);

};

var reject = function(reason) {

console.log('navigator.clipboard.readText failed: '
+reason);

};

promise["catch"](reject);

promise.then(resolve,reject)["catch"](reject);

}

else

{

console.log('This browser does not support 
navigator.clipboard.');

}

}

catch (e)

{

console.error(e,e.stack);

}

}-*/;




*public* *native* *void* writeText(String p_text)

/*-{

try

{

var _this = this;

if (navigator.clipboard)

{

console.log('navigator.clipboard.writeText()');

console.log('document.hasFocus()='+document.hasFocus());

console.log('$doc.hasFocus()='+$doc.hasFocus());

var promise = navigator.clipboard.writeText(p_text);

var resolve = function(text) {

console.log('navigator.clipboard.writeText '+text);

};

var reject = function(reason) {

console.log('navigator.clipboard.writeText failed: '
+reason);

};

promise["catch"](reject);

promise.then(resolve,reject)["catch"](reject);

}

else

{

console.log('This browser does not support 
navigator.clipboard.');

}

}

catch (e)

{

console.error(e,e.stack);

}

}-*/;

And I'm stuck on the same security error noted in that StackOverflow 
question, but with no obvious way to satisfy that requirement:

navigator.clipboard.readText()

document.hasFocus()=false

$doc.hasFocus()=true

navigator.clipboard.readText failed: NotAllowedError: Document is not 
focused.


navigator.clipboard.writeText()

document.h

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

['Jim Douglas' via GWT Users]

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
>>
>> [image: GWT-compile.png]
>>
>>
>> Here's the pom.xml file for my BBj package:
>>
>> 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 
>> "*>
>>
>> 4.0.0
>>
>> BBj
>>
>> BBj
>>
>> 19.20-SNAPSHOT
>>
>> gwt-app
>>
>> 
>>
>> 
>>
>> 
>>
>> com.google.gwt 
>>
>> gwt
>>
>> 2.8.2
>>
>> pom
>>
>> import
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>> com.google.gwt
>>
>> gwt-user
>>
>> 
>>
>> 
>>
>> com.google.gwt
>>
>> gwt-dev
>>
>> 
>>
>> 
>>
>> xml-apis
>>
>> xml-apis
>>
>> 
>>
>> 
>>
>> net.sourceforge.htmlunit
>>
>> htmlunit
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>> src
>>
>> 
>>
>> 
>>
>> src
>>
>> 
>>
>> **/*.java
>>
>> 
>>
>> 
>>
>> 
>>
>> .apt_generated
>>
>> 
>>
>> **/*.java
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>> maven-compiler-plugin
>>
>> 3.8.0
>>
>> 
>>
>> 11
>>
>> 
>>
>> 
>>
>> 
>>
>> net.ltgt.gwt.maven
>>
>> gwt-maven-plugin
>>
>> 1.0-rc-10
>>
>> true
>>
>> 
>>
>> com.basis.bbj.web.gwt.GWTWebClient
>>
>> war/WEB-INF/classes> >
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/99ba9575-75ac-4df9-ba3b-7f2595bc35c9%40googlegroups.com.

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

['Jim Douglas' via GWT Users]

(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
>
> [image: GWT-compile.png]
>
>
> Here's the pom.xml file for my BBj package:
>
> 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 
> "*>
>
> 4.0.0
>
> BBj
>
> BBj
>
> 19.20-SNAPSHOT
>
> gwt-app
>
> 
>
> 
>
> 
>
> com.google.gwt 
>
> gwt
>
> 2.8.2
>
> pom
>
> import
>
> 
>
> 
>
> 
>
> 
>
> 
>
> com.google.gwt
>
> gwt-user
>
> 
>
> 
>
> com.google.gwt
>
> gwt-dev
>
> 
>
> 
>
> xml-apis
>
> xml-apis
>
> 
>
> 
>
> net.sourceforge.htmlunit
>
> htmlunit
>
> 
>
> 
>
> 
>
> 
>
> 
>
> src
>
> 
>
> 
>
> src
>
> 
>
> **/*.java
>
> 
>
> 
>
> 
>
> .apt_generated
>
> 
>
> **/*.java
>
> 
>
> 
>
> 
>
> 
>
> 
>
> maven-compiler-plugin
>
> 3.8.0
>
> 
>
> 11
>
> 
>
> 
>
> 
>
> net.ltgt.gwt.maven
>
> gwt-maven-plugin
>
> 1.0-rc-10
>
> true
>
> 
>
> com.basis.bbj.web.gwt.GWTWebClient
>
> war/WEB-INF/classes
>
> 
>
> 
>
> 
>
> 
>
> 
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/49e18b35-cbaf-419e-861b-b451ffa7c55b%40googlegroups.com.

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

['Jim Douglas' via GWT Users]

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

[image: GWT-compile.png]


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

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"*>

4.0.0

BBj

BBj

19.20-SNAPSHOT

gwt-app







com.google.gwt 

gwt

2.8.2

pom

import











com.google.gwt

gwt-user





com.google.gwt

gwt-dev





xml-apis

xml-apis





net.sourceforge.htmlunit

htmlunit











src





src



**/*.java







.apt_generated



**/*.java











maven-compiler-plugin

3.8.0



11







net.ltgt.gwt.maven

gwt-maven-plugin

1.0-rc-10

true



com.basis.bbj.web.gwt.GWTWebClient

war/WEB-INF/classes











-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/5c1b6b87-3fce-4d89-a982-4a88a34cfa12%40googlegroups.com.

Re: Building a GWT project in Eclipse 2019-03+ with Java 11.

['Jim Douglas' via GWT Users]

Ok, after more trial and effort, this pom.xml might be workingare there 
any obvious problems with it?

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"*>

4.0.0

BBj

BBj

19.10-SNAPSHOT

gwt-app







com.google.gwt

gwt

2.8.2

pom

import











com.google.gwt

gwt-user





com.google.gwt

gwt-dev





xml-apis

xml-apis





net.sourceforge.htmlunit

htmlunit











src





src



**/*.java







.apt_generated



**/*.java











maven-compiler-plugin

3.8.0



11







net.ltgt.gwt.maven

gwt-maven-plugin

1.0-rc-10

true



com.basis.bbj.web.gwt.GWTWebClient

war/WEB-INF/classes











On Friday, August 2, 2019 at 9:50:58 AM UTC-7, Jim Douglas wrote:
>
> Ok, StackOverflow showed me 
> 
>  
> how to convert an existing Eclipse project to a Maven Project, then based 
> on your steps  1 
> and 3 I copied those chunks into the generated pom.xml (I couldn't make any 
> sense of step 2, so I skipped it). After hunting down and (I think) 
> resolving some module conflicts, that gave me this pom.xml:
>
> 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 
> "*>
>
> 4.0.0
>
> BBj
>
> BBj
>
> 19.10-SNAPSHOT
>
> 
>
> 
>
> 
>
> com.google.gwt
>
> gwt
>
> 2.8.2
>
> pom
>
> import
>
> 
>
> 
>
> 
>
> 
>
> 
>
> com.google.gwt
>
> gwt-user
>
> 
>
> 
>
> com.google.gwt
>
> gwt-dev
>
> 
>
> 
>
> xml-apis
>
> xml-apis
>
> 
>
> 
>
> net.sourceforge.htmlunit
>
> htmlunit
>
> 
>
> 
>
> 
>
> 
>
> 
>
> src
>
> 
>
> 
>
> src
>
> 
>
> **/*.java
>
> 
>
> 
>
> 
>
> .apt_generated
>
> 
>
> **/*.java
>
> 
>
> 
>
> 
>
> 
>
> 
>
> maven-compiler-plugin
>
> 3.8.0
>
> 
>
> 11
>
> 
>
> 
>
> 
>
> net.ltgt.gwt.maven
>
> gwt-maven-plugin
>
> 1.0-rc-10
>
> true
>
> 
>
> com.basis.bbj.web.gwt.GWTWebClient
>
> /BBj/war/WEB-INF/classes
>
> 
>
> 
>
> 
>
> 
>
> 
>
> What is this Eclipse error message trying to tell me?
>
> Description Resource Path Location Type
> The output directory for the project should be set to 
> /BBj/war/WEB-INF/classes BBj Unknown GWT Web App Problem
>
>
> On Thursday, August 1, 2019 at 4:34:05 AM UTC-7, Thomas Broyer wrote:
>>
>>
>>
>> On Wednesday, July 31, 2019 at 8:02:53 PM UTC+2, Jim Douglas wrote:
>>>
>>> We have a large and complex Eclipse project that uses the GWT SDK for 
>>> the GWT client stuff, and doesn't use Maven in any way at all. How would we 
>>> go about evolving that away from the GWT SDK? I know effectively nothing 
>>> about Maven. Is there some sort of instruction list somewhere to convert an 
>>> existing project, as opposed to creating a new project from scratch?
>>>
>>
>> Are you saying that you have *zero* build tool‽ not even Ant? (because 
>> Ant, with Ivy, can resolve dependencies from Maven repositories too; I have 
>> no idea how to do it myself, but there are, or have been, people here using 
>> Ivy who could possibly help)
>>  
>>
>>> I'm staring at this, and I don't know what to make of it:
>>>
>>> https://tbroyer.github.io/gwt-maven-plugin/index.html
>>>
>>> It seems to assume I already know what Maven is, I already have a Maven 
>>> project, I understand all of this obscure terminology, and I know how to 
>>> edit various configuration files...
>>>
>>
>> It does assume you already know Maven, yes.
>>  
>>
>>> and I'm just trying to find a page that says "How to install this thing."
>>>
>>
>> That's not how things work; "this thing" is a plugin for Maven, one of 
>> many plugins any Maven project will use during a build.
>> And you don't "install" it, once you have Maven installed, you only need 
>> to describe your dependencies (and plugins) in an XML file (pom.xml) and 
>> Maven will download things for you.
>>
>> But you don't need to move your whole build to using Maven only to use 
>> dependencies from a Maven repository. You could for example use Coursier 
>>  (or Maven or Ivy or Gradle or SBT) to 
>> retrieve all the JARs, and continue using your current setup for the rest.
>>  
>>
>>>
>>> On Wednesday, July 24, 2019 at 8:40:21 AM UTC-7, Thomas Broyer wrote:



 On Wednesday, July 24, 2019 at 5:14:42 PM UTC+2, Jim Douglas wrote:
>
> > Sure. Use a build tool of your choice and use the maven 
> dependencies. 
>
> I don't know what that means. As far as I've ever known, developing a 
> GWT application in Eclipse implies installing the GWT Plugin for Eclipse 
> and pi

Re: Building a GWT project in Eclipse 2019-03+ with Java 11.

['Jim Douglas' via GWT Users]

Ok, StackOverflow showed me 

 
how to convert an existing Eclipse project to a Maven Project, then based 
on your steps  1 and 
3 I copied those chunks into the generated pom.xml (I couldn't make any 
sense of step 2, so I skipped it). After hunting down and (I think) 
resolving some module conflicts, that gave me this pom.xml:

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"*>

4.0.0

BBj

BBj

19.10-SNAPSHOT







com.google.gwt

gwt

2.8.2

pom

import











com.google.gwt

gwt-user





com.google.gwt

gwt-dev





xml-apis

xml-apis





net.sourceforge.htmlunit

htmlunit











src





src



**/*.java







.apt_generated



**/*.java











maven-compiler-plugin

3.8.0



11







net.ltgt.gwt.maven

gwt-maven-plugin

1.0-rc-10

true



com.basis.bbj.web.gwt.GWTWebClient

/BBj/war/WEB-INF/classes











What is this Eclipse error message trying to tell me?

Description Resource Path Location Type
The output directory for the project should be set to 
/BBj/war/WEB-INF/classes BBj Unknown GWT Web App Problem


On Thursday, August 1, 2019 at 4:34:05 AM UTC-7, Thomas Broyer wrote:
>
>
>
> On Wednesday, July 31, 2019 at 8:02:53 PM UTC+2, Jim Douglas wrote:
>>
>> We have a large and complex Eclipse project that uses the GWT SDK for the 
>> GWT client stuff, and doesn't use Maven in any way at all. How would we go 
>> about evolving that away from the GWT SDK? I know effectively nothing about 
>> Maven. Is there some sort of instruction list somewhere to convert an 
>> existing project, as opposed to creating a new project from scratch?
>>
>
> Are you saying that you have *zero* build tool‽ not even Ant? (because 
> Ant, with Ivy, can resolve dependencies from Maven repositories too; I have 
> no idea how to do it myself, but there are, or have been, people here using 
> Ivy who could possibly help)
>  
>
>> I'm staring at this, and I don't know what to make of it:
>>
>> https://tbroyer.github.io/gwt-maven-plugin/index.html
>>
>> It seems to assume I already know what Maven is, I already have a Maven 
>> project, I understand all of this obscure terminology, and I know how to 
>> edit various configuration files...
>>
>
> It does assume you already know Maven, yes.
>  
>
>> and I'm just trying to find a page that says "How to install this thing."
>>
>
> That's not how things work; "this thing" is a plugin for Maven, one of 
> many plugins any Maven project will use during a build.
> And you don't "install" it, once you have Maven installed, you only need 
> to describe your dependencies (and plugins) in an XML file (pom.xml) and 
> Maven will download things for you.
>
> But you don't need to move your whole build to using Maven only to use 
> dependencies from a Maven repository. You could for example use Coursier 
>  (or Maven or Ivy or Gradle or SBT) to retrieve 
> all the JARs, and continue using your current setup for the rest.
>  
>
>>
>> On Wednesday, July 24, 2019 at 8:40:21 AM UTC-7, Thomas Broyer wrote:
>>>
>>>
>>>
>>> On Wednesday, July 24, 2019 at 5:14:42 PM UTC+2, Jim Douglas wrote:

 > Sure. Use a build tool of your choice and use the maven dependencies. 

 I don't know what that means. As far as I've ever known, developing a 
 GWT application in Eclipse implies installing the GWT Plugin for Eclipse 
 and picking a GWT SDK.

 http://www.gwtproject.org/usingeclipse.html

>>>
>>> Nope.
>>> Install the GWT Eclipse Plugin (
>>> https://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/Download.html;
>>>  
>>> note that the SDKs are optional).
>>> Create (
>>> https://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/maven/Maven.html)
>>>  
>>> or import (
>>> https://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/workspace/Importing.html)
>>>  
>>> a Maven project using GWT.
>>> You're all set; the plugin will use the GWT dependencies from the Maven 
>>> 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/2ecd4226-372f-4d60-83a5-9cb7f4a5f229%40googlegroups.com.

Re: Building a GWT project in Eclipse 2019-03+ with Java 11.

['Jim Douglas' via GWT Users]

We have a large and complex Eclipse project that uses the GWT SDK for the 
GWT client stuff, and doesn't use Maven in any way at all. How would we go 
about evolving that away from the GWT SDK? I know effectively nothing about 
Maven. Is there some sort of instruction list somewhere to convert an 
existing project, as opposed to creating a new project from scratch?

I'm staring at this, and I don't know what to make of it:

https://tbroyer.github.io/gwt-maven-plugin/index.html

It seems to assume I already know what Maven is, I already have a Maven 
project, I understand all of this obscure terminology, and I know how to 
edit various configuration files...and I'm just trying to find a page that 
says "How to install this thing."

On Wednesday, July 24, 2019 at 8:40:21 AM UTC-7, Thomas Broyer wrote:
>
>
>
> On Wednesday, July 24, 2019 at 5:14:42 PM UTC+2, Jim Douglas wrote:
>>
>> > Sure. Use a build tool of your choice and use the maven dependencies. 
>>
>> I don't know what that means. As far as I've ever known, developing a GWT 
>> application in Eclipse implies installing the GWT Plugin for Eclipse and 
>> picking a GWT SDK.
>>
>> http://www.gwtproject.org/usingeclipse.html
>>
>
> Nope.
> Install the GWT Eclipse Plugin (
> https://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/Download.html; 
> note that the SDKs are optional).
> Create (
> https://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/maven/Maven.html)
>  
> or import (
> https://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/workspace/Importing.html)
>  
> a Maven project using GWT.
> You're all set; the plugin will use the GWT dependencies from the Maven 
> 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/518c887f-630f-44b6-bdf6-bed2a9ea6dbf%40googlegroups.com.

Re: Building a GWT project in Eclipse 2019-03+ with Java 11.

['Jim Douglas' via GWT Users]

We have a large and complex Eclipse project that uses the GWT SDK for the 
GWT client stuff, and doesn't use Maven in any way at all. How would we go 
about evolving that away from the GWT SDK? I know effectively nothing about 
Maven. Is there some sort of instruction list somewhere to convert an 
existing project, as opposed to creating a new project from scratch?

On Wednesday, July 24, 2019 at 8:40:21 AM UTC-7, Thomas Broyer wrote:
>
>
>
> On Wednesday, July 24, 2019 at 5:14:42 PM UTC+2, Jim Douglas wrote:
>>
>> > Sure. Use a build tool of your choice and use the maven dependencies. 
>>
>> I don't know what that means. As far as I've ever known, developing a GWT 
>> application in Eclipse implies installing the GWT Plugin for Eclipse and 
>> picking a GWT SDK.
>>
>> http://www.gwtproject.org/usingeclipse.html
>>
>
> Nope.
> Install the GWT Eclipse Plugin (
> https://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/Download.html; 
> note that the SDKs are optional).
> Create (
> https://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/maven/Maven.html)
>  
> or import (
> https://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/workspace/Importing.html)
>  
> a Maven project using GWT.
> You're all set; the plugin will use the GWT dependencies from the Maven 
> 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/f330e9d4-2d92-419d-9abb-e13d231434f4%40googlegroups.com.

Re: Gwt 2.8.2 compilation error

['Jim Douglas' via GWT Users]

GWT only emulates a subset of Java classes in client-side code, and nothing 
from AWT or Swing.

http://www.gwtproject.org/doc/latest/RefJreEmulation.html

On Tuesday, July 30, 2019 at 4:56:12 PM UTC-7, medasani kesavi wrote:
>
>
> Can someone suggest if below is also for same situation
> Point2D is basic class from Java 8 however seems to be cannot be utilized 
> in GWT. Anyone using MAPs functionality experiencing the same issue
>  Line 23: Point2D cannot be resolved to a type
> [INFO]  Line 30: Point2D cannot be resolved to a type
> [INFO]  Line 30: The method normalised() from the type Line2D 
> refers to the missing type Double
> [INFO]  Line 29: Point2D cannot be resolved to a type
> [INFO]  Line 3: The import java.awt cannot be resolved
> [INFO]  Line 25: Point2D cannot be resolved to a type
> [INFO]  Line 29: The method normalised() from the type Line2D 
> refers to the missing type Double
> On Sunday, 21 July 2019 23:46:19 UTC+10, Frank Hossfeld wrote:
>>
>> The compile tells you, that there is no source code for: 
>> org.apache.commons.beanutils.PropertyUtils
>>
>> Common problem is:
>>
>> * you did not inherit the module descriptor for the module containing 
>> PropertyUtils
>>
>> Just add the module using inherits in your module descriptor. 
>>
>> But I am pretty sure, PropertyUtils can not be used on the client side 
>> ... but maybe I am wrong.
>>
>>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/5e5bf612-8f73-4506-b2d8-0836ea5ee5ba%40googlegroups.com.

Re: Building a GWT project in Eclipse 2019-03+ with Java 11.

['Jim Douglas' via GWT Users]

Umm, ok. We have an extremely large and complex GWT development environment 
here, developed over a decade; God only knows what might be involved in 
rearchitecting it to not use the GWT SDK. It's complete news to me that 
there's any alternative; I don't quite know where to start in trying to 
make sense of this configuration.

But I have to go back to my original question: Wouldn't it be theoretically 
trivial to simply strip out the offending classes from gwt-dev.jar in the 
process of publishing a GWT 2.9.0? And is there seriously no way to tell 
the "Validating GWT components" process to stop harassing me?

On Wednesday, July 24, 2019 at 8:40:21 AM UTC-7, Thomas Broyer wrote:
>
>
>
> On Wednesday, July 24, 2019 at 5:14:42 PM UTC+2, Jim Douglas wrote:
>>
>> > Sure. Use a build tool of your choice and use the maven dependencies. 
>>
>> I don't know what that means. As far as I've ever known, developing a GWT 
>> application in Eclipse implies installing the GWT Plugin for Eclipse and 
>> picking a GWT SDK.
>>
>> http://www.gwtproject.org/usingeclipse.html
>>
>
> Nope.
> Install the GWT Eclipse Plugin (
> https://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/Download.html; 
> note that the SDKs are optional).
> Create (
> https://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/maven/Maven.html)
>  
> or import (
> https://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/workspace/Importing.html)
>  
> a Maven project using GWT.
> You're all set; the plugin will use the GWT dependencies from the Maven 
> 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/00420c60-e882-4196-a842-57117110b67c%40googlegroups.com.

Re: Building a GWT project in Eclipse 2019-03+ with Java 11.

['Jim Douglas' via GWT Users]

> Sure. Use a build tool of your choice and use the maven dependencies. 

I don't know what that means. As far as I've ever known, developing a GWT 
application in Eclipse implies installing the GWT Plugin for Eclipse and 
picking a GWT SDK.

http://www.gwtproject.org/usingeclipse.html

On Wednesday, July 24, 2019 at 8:05:16 AM UTC-7, Jens wrote:
>
>
> Is there currently any way to develop a GWT application in Eclipse without 
>> using the GWT SDK?
>>
>
> Sure. Use a build tool of your choice and use the maven dependencies. 
>
> If I remember correctly the GWT plugin for eclipse will pick up the 
> gwt-user/gwt-dev jar from the class path if you have a maven/gradle project 
> in eclipse. Alternatively you can launch GWT SDM / Compiler using 
> Maven/Gradle plugins. Or you use your build tool to download all 
> dependencies and then launch GWT SDM / Compiler using a shell script.
>
> -- 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/d006b922-927b-49f2-94cf-432c0cc537de%40googlegroups.com.

Re: Building a GWT project in Eclipse 2019-03+ with Java 11.

['Jim Douglas' via GWT Users]

> Ideally, people should stop using the "GWT SDK" uberjars to begin with

Is there currently any way to develop a GWT application in Eclipse without 
using the GWT SDK?

On Wednesday, July 24, 2019 at 7:03:08 AM UTC-7, Thomas Broyer wrote:
>
> Ideally, people should stop using the "GWT SDK" uberjars to begin with; 
> because the JAR that's deployed to the Central Repository does not have 
> these packages: 
> https://github.com/gwtproject/gwt/blob/4d36d55d26aabc12e4429faf0603c539a54a13cd/maven/lib-gwt.sh#L109
>
> On Wednesday, July 24, 2019 at 9:10:46 AM UTC+2, Jens wrote:
>>
>>
>> When I configure Eclipse 2019-06 to use this modified GWT 2.8.2 SDK, i am 
>>> able to more or less get it to build, eventually, but with a flood of 
>>> obscure "Validating GWT Components" errors that have to be tediously 
>>> clicked through:
>>>
>>> An internal error occurred during: "Validating GWT components".
>>>
>>> class org.eclipse.jdt.internal.compiler.lookup.ProblemReferenceBinding 
>>> cannot be cast to class 
>>> org.eclipse.jdt.internal.compiler.lookup.PackageBinding 
>>> (org.eclipse.jdt.internal.compiler.lookup.ProblemReferenceBinding and 
>>> org.eclipse.jdt.internal.compiler.lookup.PackageBinding are in unnamed 
>>> module of loader org.eclipse.osgi.internal.loader.EquinoxClassLoader 
>>> @57cd77e1)
>>>
>>> So...first question: Did I miss an important step when I stripped those 
>>> classes out of gwt-dev.jar? Or is there a way to make "Validating GWT 
>>> components" stop complaining?
>>>
>>>
>> I don't think so. IMHO it looks like an Eclipse bug or the GWT plugin 
>> needs to be updated.
>>
>>
>> If we plan to announce that GWT 2.9 will be Java 11 compatible (syntax) 
>> then contributors will probably also sit down and make sure it works in 
>> IDEs either out of the box or by providing instructions how to configure 
>> Eclipse to make it work. In general all those 3rd party classes are 
>> included in gwt-dev.jar to just have a single dependency that needs to be 
>> added by the GWT plugin. The Maven release of GWT pulls those in as 
>> transitive dependencies. 
>>
>> I think going forward GWT SDK release (non Maven release) should 
>> repackage all those dependencies into com.google.gwt.thirdparty as it 
>> already does for some dependencies. That way we can also make sure that no 
>> dependency version conflicts exist on class path.
>>
>>
>> -- 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/f3bd66e2-2e80-4605-9306-78544afd8f6f%40googlegroups.com.

Building a GWT project in Eclipse 2019-03+ with Java 11.

['Jim Douglas' via GWT Users]

As of Eclipse 2019-03, Eclipse started to strictly enforce JLS §7.4.3 
 
(7.4.3. 
Package Observability and Visibility), as discussed here:

https://stackoverflow.com/questions/51094274/eclipse-cant-find-xml-related-classes-after-switching-build-path-to-jdk-10

https://bugs.eclipse.org/bugs/show_bug.cgi?id=544758

This means that when building with Java 11, any Eclipse package with a 
classpath that contains any classes that are also defined in the JDK will 
now report a flood of build errors in the format:

"The package org.w3c.dom is accessible from more than one module: 
, jdk.xml.dom" 

My GWT project uses classes that are defined in these Java 11 modules:

https://docs.oracle.com/en/java/javase/11/docs/api/java.xml/module-summary.html

https://docs.oracle.com/en/java/javase/11/docs/api/jdk.jsobject/module-summary.html

It turns out that gwt-dev.jar contains several hundred classes that 
conflict with Java 11 internal modules. In an attempt to hack around this, 
I made a copy of the gwt-2.8.2 folder and stripped out the offending 
classes:

scrappy:gwt-2.8.2-mod jimdouglas$ zip -d gwt-dev.jar "org/w3c/*" 
"org/xml/*" "javax/xml/*" "netscape/javascript/*"

When I configure Eclipse 2019-06 to use this modified GWT 2.8.2 SDK, i am 
able to more or less get it to build, eventually, but with a flood of 
obscure "Validating GWT Components" errors that have to be tediously 
clicked through:

An internal error occurred during: "Validating GWT components".

class org.eclipse.jdt.internal.compiler.lookup.ProblemReferenceBinding 
cannot be cast to class 
org.eclipse.jdt.internal.compiler.lookup.PackageBinding 
(org.eclipse.jdt.internal.compiler.lookup.ProblemReferenceBinding and 
org.eclipse.jdt.internal.compiler.lookup.PackageBinding are in unnamed 
module of loader org.eclipse.osgi.internal.loader.EquinoxClassLoader 
@57cd77e1)

So...first question: Did I miss an important step when I stripped those 
classes out of gwt-dev.jar? Or is there a way to make "Validating GWT 
components" stop complaining?

And moving forward, are there plans for a GWT 2.9.0, and would it be 
possible for it to incorporate some version of this hack, or whatever other 
changes are necessary to enable GWT development in Eclipse with Java 11? 
(N.B. I don't particularly care about Java 11 syntax support, just minimal 
build ability.)

[image: ValidatingGWTComponents.png]

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/9482a0db-8156-417c-bfef-1a40f3b17f33%40googlegroups.com.

Re: Regarding Spellcheck in GWT RichtextArea

['Jim Douglas' via GWT Users]

Define "not working"?

In a quick test here, it appears to inherit your browser's spell check 
language settings:

http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwRichText

GWT 2.6.0 is more than five years old; the current released version is 
2.8.2.

http://www.gwtproject.org/download.html

On Thursday, April 25, 2019 at 6:33:31 AM UTC-7, mallig...@gmail.com wrote:
>
> Hello All,
>
> Here I am using GWT RichtextArea, in this editor spell check is not 
> working and my gwt version 2.6.0,
>
> Please help with any suggestions
>
> Thanks in advance..!
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.