Re: Is there some description anywhere how to set up a decently usable GWT 2.10 development environment?
y 10 and jetty plugin and java 17. This is what we >>>> have now. The GWT configuration is a tiny bit different as GWT 2.10.0 can >>>> only handle Java 11 right now, not Java 17. >>>> >>>> We never found the need to use the jetty plugin until we needed to use >>>> WebSocket and jetty 9.2 can't handle WebSocket very well. There was a way >>>> to get around it, but unfortunately that way was blocked by Java 9 and up. >>>> A year ago, I found out about that site. I followed the instructions from >>>> that site and got everything working with some changes, as my source code >>>> structure is different from his. >>>> >>>> Let me know if you encountered an issue you can't solve. I don't check >>>> the mailbox of this email address, so posting the questions here is >>>> better. >>>> If this is the right way to go about this in this group. >>>> >>>> We have been using GWT since the beginning, for almost 15 years now. We >>>> started using jetty about 8 years ago; before that, we were using Tomcat >>>> (and Apache). We migrated from Eclipse to IntelliJ about 3 years ago. We >>>> never use maven as we need to be able to build the whole system with >>>> everything included in a repo (except Java). Just a weird requirement, >>>> that >>>> is for sure. So, we are still using ant to build our war file as well. >>>> >>>> On Wednesday, December 14, 2022 at 12:53:35 PM UTC-5 nam...@gmail.com >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> We succesfully use the gwt 2.10 dev mode to run and debug our >>>>> applications. We had to overide the JettyLauncher class to be able to run >>>>> it with java > 8. >>>>> What kind of issue do you have with the dev mode (with gwt plugin on >>>>> eclipse) ? >>>>> >>>>> Le mer. 14 déc. 2022 à 18:22, mmo a écrit : >>>>> >>>>>> Over the last years our GWT development environment has eroded more >>>>>> and more. >>>>>> First the browser plugins seized to work, then the >>>>>> mapping/JS-code-backtranslation stopped working and recently also the >>>>>> IDE >>>>>> plugins for Eclipse and IntelliJ that would deploy the generated >>>>>> artifacts >>>>>> to the correct places, start the code server and allowed some >>>>>> minimalistic >>>>>> form of debugging seized to work. It is getting more and more not just >>>>>> frustrating but really horrible and "mission impossible". >>>>>> >>>>>> Thus a while ago I began an effort to port our application to GWT >>>>>> 2.10 and Java 8 (our "production version" still runs with GWT 2.7 and >>>>>> Java >>>>>> 7 and I can't go to higher Java versions due to some libraries, yet). >>>>>> >>>>>> Meanwhile I found my way through all the library conflicts so that I >>>>>> am able to build and generate a version that runs fine when deploying >>>>>> the >>>>>> generated .war file to to a Tomcat Server (v8.5 in our case). >>>>>> >>>>>> But being able to building a running version is one thing. The other >>>>>> is to have a development setup that doesn't shy away developers crying >>>>>> and >>>>>> yelling but allows to do decent client side code debugging. >>>>>> >>>>>> With the "old" GWT plugin the commands "gwt:run" and "gwt:debug" >>>>>> didn't work anymore with GWT 2.10. I keep getting the following error >>>>>> during Jetty startup: >>>>>> >>>>>> java.lang.IllegalArgumentException: Object of class >>>>>> 'com.google.gwt.dev.shell.jetty.JettyLauncher.WebAppContextWithReload' >>>>>> is >>>>>> not of type 'org.eclipse.jetty.webapp.WebAppContext'. >>>>>> Object Class and type Class are from different loaders. in >>>>>> file:///D:/Projects/our-app/our-app-web/target/our-app/WEB-INF/jetty-web.xml >>>>>> at >>>>>> org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:421) >>>&
Is there some description anywhere how to set up a decently usable GWT 2.10 development environment?
Over the last years our GWT development environment has eroded more and more. First the browser plugins seized to work, then the mapping/JS-code-backtranslation stopped working and recently also the IDE plugins for Eclipse and IntelliJ that would deploy the generated artifacts to the correct places, start the code server and allowed some minimalistic form of debugging seized to work. It is getting more and more not just frustrating but really horrible and "mission impossible". Thus a while ago I began an effort to port our application to GWT 2.10 and Java 8 (our "production version" still runs with GWT 2.7 and Java 7 and I can't go to higher Java versions due to some libraries, yet). Meanwhile I found my way through all the library conflicts so that I am able to build and generate a version that runs fine when deploying the generated .war file to to a Tomcat Server (v8.5 in our case). But being able to building a running version is one thing. The other is to have a development setup that doesn't shy away developers crying and yelling but allows to do decent client side code debugging. With the "old" GWT plugin the commands "gwt:run" and "gwt:debug" didn't work anymore with GWT 2.10. I keep getting the following error during Jetty startup: java.lang.IllegalArgumentException: Object of class 'com.google.gwt.dev.shell.jetty.JettyLauncher.WebAppContextWithReload' is not of type 'org.eclipse.jetty.webapp.WebAppContext'. Object Class and type Class are from different loaders. in file:///D:/Projects/our-app/our-app-web/target/our-app/WEB-INF/jetty-web.xml at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:421) ... I also read in this forum that other people had issues with GWT 2.10 and Jetty (and that the maintainers of GWT are aware of that but don't plan to fix this) so I guess it's time to switch to deploying to Tomcat, instead. Probably I also will switch to the new GWT plugin (by T.Broyer). I already tried it and I can at least build the same .war file using it. But how do I set this while thing up to provide a better developer experience? Is there some example or description of how to deploy a GWT 2.10 application to a Tomcat server in development mode (i.e. with code server and - if possible - hot code replacement, etc.)? How can GWT development be made "convenient" or at least acceptable again? Any pointers, descriptions or examples would be highly appreciated! -- 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/d2fd58f0-f5e7-4a2b-9320-45d5ec244379n%40googlegroups.com.
Re: GWT compiler keeps complaining about missing source files
@Jens: Thanks such a lot for spotting this! I am such an idiot! @t.br...@gmail.com: Thanks for the advice as well. I indeed went that route after having first fixed my paths (above) but which then caused compile errors in the server side code (because my dropped-in classes conflicted with the original ones causing compile errors for the server side code). Thanks again both! I really appreciate your support! On Tuesday, July 26, 2022 at 3:22:02 PM UTC+2 Jens wrote: > The GwtSpring.gwt.xml reads: >> --- >> >> >> >> >> >> >> >> >> >> >> >> ... further details omitted here ... >> > > > > Use slash instead of dots in path="security.core" and > path="security.core.userdetails" > > -- 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/a3e05bcb-0e41-4188-beda-1f0b820b2e52n%40googlegroups.com.
Re: GWT compiler keeps complaining about missing source files
Originally I had indeed placed all the code (also the "drop-ins" for Spring) under src/main/java but I then got the very same errors as described in my previous email. And also now, after I have moved them back into the java sub-tree I keep getting the same error. So, there must be something else still wrong here... ?!? I provide an updated view of how my java source and resource tree currently looks like. * | +-* src | +-* main | | +-* java | | | +-* ch | | | | +-* zh | | | | | +-* registerjp | | | | | | +-* client | | | | | | | +-- ... | | | | | | +-* shared | | | | | | | +-* security | | | | | | | | +-- ZHStRegisterJPUser.java | | | | | | | | +-- ... | | | | | | | +-- ... | | | | | | +-* server | | | | | | | +-- ... | | | +-* org<< copies of the referenced Spring source files below this folder | | | | +-* springframework | | | | | +-* security | | | | | | +-* core | | | | | | | +-- GrantedAuthority.java | | | | | | | +-- CredentialsContainer.java | | | | | | | +-- ... | | | | | | | +-* userdetails | | | | | | | | +-- User.java | | | | | | | | +-- UserDetails.java | | ... | | +-* resource | | | +-* ch | | | | +-* zh | | | | | +-* registerjp | | | | | | +-- ZHStRegisterJPWeb.gwt.xml << our application's gwt-file | | | | | ... | | | | | | | +-* org | | | | +-* springframework | | | | | +-- GwtSpring.gwt.xml << the added Spring gwt-file | | | ... [Note: '*' are directories] On Tuesday, July 26, 2022 at 11:42:56 AM UTC+2 peter.j...@gmail.com wrote: > It looks like you put the source in the resources tree rather than in the > source tree. If you fix that then it may help > > On Tue, Jul 26, 2022 at 6:21 PM mmo wrote: > >> In the code that I inherited my predecessors had decided to use a couple >> of Spring classes even in GWT client code. >> While I am not exactly enthused by this decision the referenced classes >> are - at least from my point of view - OK to use in GWT client code, since >> they are mostly interfaces or simple classes that don't pull too much of >> "Spring" into the client. So my aim is to leave the code as such unchanged >> as much as possible (trying to follow the "never change running >> code"-principle...). >> >> What I don't like, however, is that so far they had simply ignored the >> resulting GWT compile errors. I am thus now trying to correct the GWT >> settings such that this at least compiles without errors (i.e. that I can >> use the "strict" compiler setting). >> >> The initial error was that the Spring sources for GrantedAuthority, >> CredentialsContainer and a few more classes could not be found during GWT >> compilation. >> When I then added the Spring sources jar to the dependencies the GWT >> compiler ran havock and apparently tried to compile the ENTIRE Spring >> library. That was definitely NOT what I wanted. >> Next I tried to provide ONLY (copies of) those sources that are actually >> referenced in our GWT code, i.e. I added copies of those spring source >> files to our resources folder and try to direct the GWT compiler to use >> only those. Besides the mentioned java files I thus also added a >> GwtSpring.gwt.xml file which I reference from our application's >> ZHStRegisterJPWeb.gwt.xml like so: >> >> >> * >> | >> +-* src >> | +-* main >> | | +-* java >> | | | +-* ch >> | | | | +-* zh >> | | | | | +-* registerjp >> | | | | | | +-* client >> | | | | | | | +-- ... >> | | | | | | +-* shared >> | | | | | | | +-* security >> | | | | | | | | +-- ZHStRegisterJPUser.java >> | | | | | | | | +-- ... >> | | | | | | | +-- ... >> | | | | | | +-* server >> | | | | | | | +-- ... >> | | | >> | | +-* resource >> | | | +-* ch >> | | | | +-* zh >> | | | | | +-* registerjp >> | | | | | | +-- ZHStRegisterJPWeb.gwt.xml << our application's gwt-file >> | | | | | ... >> | | | | >> | | | +-* org >> | | | | +-* springframework >> | | | | | +-- GwtSpring.gwt.xml << the added Spring gwt-file >> | | | | | +-* security << copies of the referenced Spring source files >> below this folder >> | | | | | | +-* core >> | | | | | | | +-- GrantedAuthority.java >> | | | | | | | +-- CredentialsContainer.java >> | | | | | | | +-- ... >> | | | | | | | +-* userdetails >> | | | | | | | | +-- User.java >> | | | | | | | | +-- UserDetails.java >> | | | ... >> >> [Note: '*' are directories] >> >> >> The ZHStRegisterJPWeb.gwt.xml reads: >> --- >> >> >> >> >> >> >> >> >> .
GWT compiler keeps complaining about missing source files
In the code that I inherited my predecessors had decided to use a couple of Spring classes even in GWT client code. While I am not exactly enthused by this decision the referenced classes are - at least from my point of view - OK to use in GWT client code, since they are mostly interfaces or simple classes that don't pull too much of "Spring" into the client. So my aim is to leave the code as such unchanged as much as possible (trying to follow the "never change running code"-principle...). What I don't like, however, is that so far they had simply ignored the resulting GWT compile errors. I am thus now trying to correct the GWT settings such that this at least compiles without errors (i.e. that I can use the "strict" compiler setting). The initial error was that the Spring sources for GrantedAuthority, CredentialsContainer and a few more classes could not be found during GWT compilation. When I then added the Spring sources jar to the dependencies the GWT compiler ran havock and apparently tried to compile the ENTIRE Spring library. That was definitely NOT what I wanted. Next I tried to provide ONLY (copies of) those sources that are actually referenced in our GWT code, i.e. I added copies of those spring source files to our resources folder and try to direct the GWT compiler to use only those. Besides the mentioned java files I thus also added a GwtSpring.gwt.xml file which I reference from our application's ZHStRegisterJPWeb.gwt.xml like so: * | +-* src | +-* main | | +-* java | | | +-* ch | | | | +-* zh | | | | | +-* registerjp | | | | | | +-* client | | | | | | | +-- ... | | | | | | +-* shared | | | | | | | +-* security | | | | | | | | +-- ZHStRegisterJPUser.java | | | | | | | | +-- ... | | | | | | | +-- ... | | | | | | +-* server | | | | | | | +-- ... | | | | | +-* resource | | | +-* ch | | | | +-* zh | | | | | +-* registerjp | | | | | | +-- ZHStRegisterJPWeb.gwt.xml << our application's gwt-file | | | | | ... | | | | | | | +-* org | | | | +-* springframework | | | | | +-- GwtSpring.gwt.xml << the added Spring gwt-file | | | | | +-* security << copies of the referenced Spring source files below this folder | | | | | | +-* core | | | | | | | +-- GrantedAuthority.java | | | | | | | +-- CredentialsContainer.java | | | | | | | +-- ... | | | | | | | +-* userdetails | | | | | | | | +-- User.java | | | | | | | | +-- UserDetails.java | | | ... [Note: '*' are directories] The ZHStRegisterJPWeb.gwt.xml reads: --- ... further details omitted here ... --- The GwtSpring.gwt.xml reads: --- ... further details omitted here ... --- However, the GWT compiler STILL complains that it can not locate the sources of GrantedAuthority and other Spring classes: ... [INFO]Tracing compile failure path for type 'ch.zh.ksta.zhstregisterjp.shared.security.ZHStRegisterJPUser' [INFO] [ERROR] Errors in 'ch/zh/ksta/zhstregisterjp/shared/security/ZHStRegisterJPUser.java' [INFO] [ERROR] Line 40: No source code is available for type org.springframework.security.core.userdetails.User; did you forget to inherit a required module? [INFO] [ERROR] Line 94: No source code is available for type org.springframework.security.core.GrantedAuthority; did you forget to inherit a required module? ... Any idea why it doesn't find these files even though I now provide them explicitly? What am I missing here? -- 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/cffab879-e6ac-4aac-9fe1-cabcaac72d0an%40googlegroups.com.
Re: How interpret error messages?
Sorry - if you get this twice - I accidentally have hit the PostMessage button before and had to delete the message again. Just tried to dig deeper here: the gwt-user.jar contains a file /org/hibernate/validator/HibernateValidator.gwt.xml. In the GWT-file I see a section ... ... The file engine/NodeImpl.[java|class] however, is not in that .jar. Where's that supposed to come from? On Thursday, July 21, 2022 at 6:39:11 PM UTC+2 mmo wrote: > When I compile my application with failOnError=true and logLevel=TRACE I > see errors like this: > > ... > [INFO]Tracing compile failure path for type > 'org.hibernate.validator.engine.PathImpl' > [INFO] [ERROR] Errors in > 'jar:file:/D:/m2repository/rjp/org/gwtproject/gwt-user/2.10.0/gwt-user-2.10.0.jar!/org/hibernate/validator/super/org/hibernate/validator/engine/PathImpl.java' > [INFO] [ERROR] Line 202: The constructor NodeImpl(String) is > undefined > [INFO] [ERROR] Line 95: The constructor NodeImpl(Path.Node) is > undefined > [INFO] [ERROR] Line 209: The method setIndex(Integer) is > undefined for the type NodeImpl > [INFO] [ERROR] Line 212: The method setKey(String) is undefined > for the type NodeImpl > [INFO] [ERROR] Line 72: The constructor NodeImpl(String) is > undefined > [INFO] [ERROR] Line 84: The constructor NodeImpl(Path.Node) is > undefined > [INFO] [ERROR] Line 204: The method setInIterable(boolean) is > undefined for the type NodeImpl > ... > > How does one interpret these? It seems to me as if the > ...org/gwtproject/gwt-user/2.10.0/gwt-user-2.10.0.jar references some > class org/hibernate/validator/engine/PathImpl.java and can't find its > source. > Is that intgerpretation correct? If so: what do I need to import to make > that source available? Certainly not the entire Hibernate sources, do I? > -- 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/fd706bc9-8c8d-4514-b0f9-45f18639289bn%40googlegroups.com.
Re: How interpret error messages?
Just tried to dig deeper here: the gwt-user.jar contains a file /org/hibernate/validator/HibernateValidator.gwt.xml. In the GWT-file I see a section ... ... The File NodeImpl.java, however, is NOT contained in that .jar. On Thursday, July 21, 2022 at 6:39:11 PM UTC+2 mmo wrote: > When I compile my application with failOnError=true and logLevel=TRACE I > see errors like this: > > ... > [INFO]Tracing compile failure path for type > 'org.hibernate.validator.engine.PathImpl' > [INFO] [ERROR] Errors in > 'jar:file:/D:/m2repository/rjp/org/gwtproject/gwt-user/2.10.0/gwt-user-2.10.0.jar!/org/hibernate/validator/super/org/hibernate/validator/engine/PathImpl.java' > [INFO] [ERROR] Line 202: The constructor NodeImpl(String) is > undefined > [INFO] [ERROR] Line 95: The constructor NodeImpl(Path.Node) is > undefined > [INFO] [ERROR] Line 209: The method setIndex(Integer) is > undefined for the type NodeImpl > [INFO] [ERROR] Line 212: The method setKey(String) is undefined > for the type NodeImpl > [INFO] [ERROR] Line 72: The constructor NodeImpl(String) is > undefined > [INFO] [ERROR] Line 84: The constructor NodeImpl(Path.Node) is > undefined > [INFO] [ERROR] Line 204: The method setInIterable(boolean) is > undefined for the type NodeImpl > ... > > How does one interpret these? It seems to me as if the > ...org/gwtproject/gwt-user/2.10.0/gwt-user-2.10.0.jar references some > class org/hibernate/validator/engine/PathImpl.java and can't find its > source. > Is that intgerpretation correct? If so: what do I need to import to make > that source available? Certainly not the entire Hibernate sources, do I? > -- 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/7f66aff9-0ca0-40be-b31b-a7603a823d21n%40googlegroups.com.
How interpret error messages?
When I compile my application with failOnError=true and logLevel=TRACE I see errors like this: ... [INFO]Tracing compile failure path for type 'org.hibernate.validator.engine.PathImpl' [INFO] [ERROR] Errors in 'jar:file:/D:/m2repository/rjp/org/gwtproject/gwt-user/2.10.0/gwt-user-2.10.0.jar!/org/hibernate/validator/super/org/hibernate/validator/engine/PathImpl.java' [INFO] [ERROR] Line 202: The constructor NodeImpl(String) is undefined [INFO] [ERROR] Line 95: The constructor NodeImpl(Path.Node) is undefined [INFO] [ERROR] Line 209: The method setIndex(Integer) is undefined for the type NodeImpl [INFO] [ERROR] Line 212: The method setKey(String) is undefined for the type NodeImpl [INFO] [ERROR] Line 72: The constructor NodeImpl(String) is undefined [INFO] [ERROR] Line 84: The constructor NodeImpl(Path.Node) is undefined [INFO] [ERROR] Line 204: The method setInIterable(boolean) is undefined for the type NodeImpl ... How does one interpret these? It seems to me as if the ...org/gwtproject/gwt-user/2.10.0/gwt-user-2.10.0.jar references some class org/hibernate/validator/engine/PathImpl.java and can't find its source. Is that intgerpretation correct? If so: what do I need to import to make that source available? Certainly not the entire Hibernate sources, do I? -- 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/471e8f9b-4a3b-43f1-8df0-61af6b02b7a0n%40googlegroups.com.
Re: Startup error: Object of class 'com.google.gwt.dev.shell.jetty.JettyLauncher.WebAppContextWithReload' is not of type 'org.eclipse.jetty.webapp.WebAppContext'.
OK - thanks for letting me know! I interpret that such that gwt:run and
gwt:debug aren't working/supported anymore, right?
Do you test and develop in a Tomcat or what's your preferred setup?
On Thursday, July 21, 2022 at 1:33:53 PM UTC+2 t.br...@gmail.com wrote:
> If you need anything specific, don't use the embedded Jetty.
> You have a jetty-web.xml so I assume you need "something specific" → don't
> use the embedded Jetty.
>
> (it might be that this was plain broken in 2.10 when upgrading the Jetty
> version, but the last time I had to work on this –that was years ago–, I
> declared it was the last time and jetty-web.xml wouldn't be supported in
> the future: if it works, you're lucky, if it doesn't, well, we never said
> it would so 路 ; now other maintainers might have a different opinion and
> would be willing to investigate)
>
> On Wednesday, July 20, 2022 at 9:30:16 PM UTC+2 mmo wrote:
>
>> After some substantial fiddling and bug chasing I finally managed to
>> successfully compile our application using GWT 2.10.0. However, when I
>> start this locally using the command line:
>>
>> mvn -s
>> "D:\Projects\KStA_ZH_RegisterJP\code\application\etc\m2\settings_mms.xml"
>> "gwt:run" -f
>> "D:\Projects\KStA_ZH_RegisterJP\code\application\zhstregisterjp-web\pom.xml"
>>
>> (I am using powershell, that's why I need all those quotes)
>>
>> ... then the Jetty-startup ends in:
>>
>> ...
>> 00:00:11.918 [WARN] Failed startup of context
>> c.g.g.d.s.j.WebAppContextWithReload@aa5455e{/,file:///D:/Projects/KStA_ZH_RegisterJP/code/application/zhstregisterjp-web/target/registerjp/,UNAVAILABLE}{D:\Projects\KStA_ZH_RegisterJP\code\application\zhstregisterjp-web\target\registerjp}
>> java.lang.IllegalArgumentException: Object of class
>> 'com.google.gwt.dev.shell.jetty.JettyLauncher.WebAppContextWithReload' is
>> not of type 'org.eclipse.jetty.webapp.WebAppContext'.
>> Object Class and type Class are from different loaders. in
>> file:///D:/Projects/KStA_ZH_RegisterJP/code/application/zhstregisterjp-web/target/registerjp/WEB-INF/jetty-web.xml
>>
>> What am I missing here or what needs to be changed to get this running
>> again with v2.10? Could some kind soul give me a nudge in the direction to
>> search for?
>>
>
--
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/6fa9c53e-b80d-49a1-9ff8-1240f9bc69fan%40googlegroups.com.
Startup error: Object of class 'com.google.gwt.dev.shell.jetty.JettyLauncher.WebAppContextWithReload' is not of type 'org.eclipse.jetty.webapp.WebAppContext'.
After some substantial fiddling and bug chasing I finally managed to
successfully compile our application using GWT 2.10.0. However, when I
start this locally using the command line:
mvn -s
"D:\Projects\KStA_ZH_RegisterJP\code\application\etc\m2\settings_mms.xml"
"gwt:run" -f
"D:\Projects\KStA_ZH_RegisterJP\code\application\zhstregisterjp-web\pom.xml"
(I am using powershell, that's why I need all those quotes)
... then the Jetty-startup ends in:
...
00:00:11.918 [WARN] Failed startup of context
c.g.g.d.s.j.WebAppContextWithReload@aa5455e{/,file:///D:/Projects/KStA_ZH_RegisterJP/code/application/zhstregisterjp-web/target/registerjp/,UNAVAILABLE}{D:\Projects\KStA_ZH_RegisterJP\code\application\zhstregisterjp-web\target\registerjp}
java.lang.IllegalArgumentException: Object of class
'com.google.gwt.dev.shell.jetty.JettyLauncher.WebAppContextWithReload' is
not of type 'org.eclipse.jetty.webapp.WebAppContext'.
Object Class and type Class are from different loaders. in
file:///D:/Projects/KStA_ZH_RegisterJP/code/application/zhstregisterjp-web/target/registerjp/WEB-INF/jetty-web.xml
What am I missing here or what needs to be changed to get this running
again with v2.10? Could some kind soul give me a nudge in the direction to
search for?
--
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/51c8897c-c981-4461-91c1-f8e79cf22ce0n%40googlegroups.com.
Re: Compatibility of GWT 2.10.0 with GXT 2.3.1.a
> We have fixed some things on GXT 2.3.1a. With some fixes, you can run perfectly the GXT 2.3.1a in GWT 2.2+ (GWT 2.9.0 and 2.10.0 included). Would you mind to elaborate on these fixes? Have you documented these somewhere? On Monday, July 18, 2022 at 6:05:57 PM UTC+2 Ricardo Serathiuk wrote: > I work with an application using GWT 2.10.0 and GXT 2.3.1a. We have fixed > some things on GXT 2.3.1a. With some fixes, you can run perfectly the GXT > 2.3.1a in GWT 2.2+ (GWT 2.9.0 and 2.10.0 included). > -- 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/a4aa86c7-d74a-48ef-a6c0-d687be2018aan%40googlegroups.com.
Re: 'Throwable.HasJavaThrowable' has invalid name '?'.
Pardon my ignorance but I never had to dive very deeply into many of these GWT details and options, yet. Is that "-strict" that Michael and you mention the same as setting: gwt-maven-plugin ... ... true ... in a pom.xml? I searched for strict in the maven plugin's description and this seems to be the only match I found. Anyway - after settings said option I got much more GWT compiler output and there are tons of error messages with the pattern "No source code is available for type . did you forget to inherit a required module". Unfortunately, the classes referenced are misc. stuff from com.google.gwt.user, com.google.common.collect, org.apache.commons.collections, org.springframework.security.core, etc., i.e. all classes that I can not shift into the UI's shared or client folder. How can one make the sources of these classes known to the GWT compiler? On Wednesday, June 29, 2022 at 11:05:06 PM UTC+2 Jens wrote: > Yeah as Michael already said, I strongly encourage you to use "-strict" > GWT compiler / DevMode parameter in all of your GWT projects and fix all > GWT compile errors you are then seeing. We should have make that parameter > the default setting long time ago. I really don't see any benefit of not > using it. > > The error you are seeing indicates that you have an old GWT 2.8.0 on your > class path which is used for compilation. GWT 2.8.0 does not know anything > about "*" or "?" as native JsInterop type names and thus disallows them. > Both names have been implemented in GWT 2.8.1+ and have a special meaning. > > See: > https://github.com/gwtproject/gwt/commit/d458a94f2810ab8e340b76bcf17fbbe0a72b188f > > So use -strict to see GWT compilation errors that need to be fixed and > check your classpath so that you really only have one GWT SDK version. > > -- J. > > mmo schrieb am Mittwoch, 29. Juni 2022 um 19:10:09 UTC+2: > >> When compiling one of our GWT-based projects with the new GWT 2.10.0 I >> get: >> >> ... >> [INFO] --- gwt-maven-plugin:2.10.0:compile (default) @ zhstregisterjp-web >> --- >> [INFO] Compiling module >> ch.zh.ksta.zhstregisterjp.ZHStRegisterJPWebDevelopment >> [INFO]Ignored 5 units with compilation errors in first pass. >> [INFO] Compile with -strict or with -logLevel set to DEBUG or WARN to see >> all errors. >> [INFO]Ignored 14 units with compilation errors in first pass. >> [INFO] Compile with -strict or with -logLevel set to TRACE or DEBUG to >> see all errors. >> [INFO]Errors in com/google/gwt/emul/java/lang/Throwable.java >> [INFO] [ERROR] Line 344: 'Throwable.HasJavaThrowable' has invalid >> name '?'. >> >> Pardon me? >> >> Any hint or direction what I could do or search for here to get over this? >> > -- 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/a28aadb5-904b-44a7-8039-7da5684ca6f3n%40googlegroups.com.
Re: java.lang.IllegalArgumentException at org.objectweb.asm.ClassVisitor.
As an experiment I removed an old exclusion of com.google.gwt:gwt-dev that some job-ancestor of mine had specified (see the commented part in my pom.xml snippet below): ... com.gwtplatform gwtp-mvp-client 1.6 ... and now I don't get the mentioned compiler error anymore but instead I end in the same odd 'Throwable.HasJavaThrowable' has invalid name '?' exception that I describe in my other thread. So, both, project migrations are now stuck in the same issue ... :-( On Wednesday, June 29, 2022 at 7:16:10 PM UTC+2 mmo wrote: > The compilation of the other application I am trying to migrate to GWT > 2.10.0 fails this stacktrace: > > ... > [INFO] --- gwt-maven-plugin:2.10.0:compile (default) @ zhquest-web --- > [INFO] Compiling module ch.zh.ksta.zhquest.ZHQuestWebDevelopment > [INFO] [ERROR] Unexpected internal compiler error > [INFO] java.lang.IllegalArgumentException > [INFO] at org.objectweb.asm.ClassVisitor.(Unknown Source) > [INFO] at org.objectweb.asm.ClassVisitor.(Unknown Source) > [INFO] at > com.google.gwt.dev.javac.BytecodeSignatureMaker$CompileDependencyVisitor.(BytecodeSignatureMaker.java:59) > [INFO] at > com.google.gwt.dev.javac.BytecodeSignatureMaker.visitCompileDependenciesInBytecode(BytecodeSignatureMaker.java:227) > [INFO] at > com.google.gwt.dev.javac.BytecodeSignatureMaker.getCompileDependencySignature(BytecodeSignatureMaker.java:209) > [INFO] at > com.google.gwt.dev.javac.CompiledClass.getSignatureHash(CompiledClass.java:166) > [INFO] at > com.google.gwt.dev.javac.Dependencies$Ref.(Dependencies.java:41) > [INFO] at > com.google.gwt.dev.javac.Dependencies$Ref.(Dependencies.java:36) > [INFO] at > com.google.gwt.dev.javac.Dependencies.resolve(Dependencies.java:100) > [INFO] at > com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater.compile(CompilationStateBuilder.java:349) > [INFO] at > com.google.gwt.dev.javac.CompilationStateBuilder.doBuildFrom(CompilationStateBuilder.java:532) > [INFO] at > com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:464) > [INFO] at > com.google.gwt.dev.cfg.ModuleDef.getCompilationState(ModuleDef.java:423) > [INFO] at com.google.gwt.dev.Precompile.precompile(Precompile.java:210) > [INFO] at com.google.gwt.dev.Precompile.precompile(Precompile.java:190) > [INFO] at com.google.gwt.dev.Precompile.precompile(Precompile.java:131) > [INFO] at com.google.gwt.dev.Compiler.compile(Compiler.java:192) > [INFO] at com.google.gwt.dev.Compiler.compile(Compiler.java:143) > [INFO] at com.google.gwt.dev.Compiler.compile(Compiler.java:132) > [INFO] at com.google.gwt.dev.Compiler$1.run(Compiler.java:110) > [INFO] at > com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java:55) > [INFO] at > com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRunner.java:50) > [INFO] at com.google.gwt.dev.Compiler.main(Compiler.java:113) > > > Any hint on this would also be highly appreciated. > > Michael > > -- 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/69257efa-3ca8-4f91-90be-adf598100193n%40googlegroups.com.
java.lang.IllegalArgumentException at org.objectweb.asm.ClassVisitor.
The compilation of the other application I am trying to migrate to GWT 2.10.0 fails this stacktrace: ... [INFO] --- gwt-maven-plugin:2.10.0:compile (default) @ zhquest-web --- [INFO] Compiling module ch.zh.ksta.zhquest.ZHQuestWebDevelopment [INFO] [ERROR] Unexpected internal compiler error [INFO] java.lang.IllegalArgumentException [INFO] at org.objectweb.asm.ClassVisitor.(Unknown Source) [INFO] at org.objectweb.asm.ClassVisitor.(Unknown Source) [INFO] at com.google.gwt.dev.javac.BytecodeSignatureMaker$CompileDependencyVisitor.(BytecodeSignatureMaker.java:59) [INFO] at com.google.gwt.dev.javac.BytecodeSignatureMaker.visitCompileDependenciesInBytecode(BytecodeSignatureMaker.java:227) [INFO] at com.google.gwt.dev.javac.BytecodeSignatureMaker.getCompileDependencySignature(BytecodeSignatureMaker.java:209) [INFO] at com.google.gwt.dev.javac.CompiledClass.getSignatureHash(CompiledClass.java:166) [INFO] at com.google.gwt.dev.javac.Dependencies$Ref.(Dependencies.java:41) [INFO] at com.google.gwt.dev.javac.Dependencies$Ref.(Dependencies.java:36) [INFO] at com.google.gwt.dev.javac.Dependencies.resolve(Dependencies.java:100) [INFO] at com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater.compile(CompilationStateBuilder.java:349) [INFO] at com.google.gwt.dev.javac.CompilationStateBuilder.doBuildFrom(CompilationStateBuilder.java:532) [INFO] at com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:464) [INFO] at com.google.gwt.dev.cfg.ModuleDef.getCompilationState(ModuleDef.java:423) [INFO] at com.google.gwt.dev.Precompile.precompile(Precompile.java:210) [INFO] at com.google.gwt.dev.Precompile.precompile(Precompile.java:190) [INFO] at com.google.gwt.dev.Precompile.precompile(Precompile.java:131) [INFO] at com.google.gwt.dev.Compiler.compile(Compiler.java:192) [INFO] at com.google.gwt.dev.Compiler.compile(Compiler.java:143) [INFO] at com.google.gwt.dev.Compiler.compile(Compiler.java:132) [INFO] at com.google.gwt.dev.Compiler$1.run(Compiler.java:110) [INFO] at com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java:55) [INFO] at com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRunner.java:50) [INFO] at com.google.gwt.dev.Compiler.main(Compiler.java:113) Any hint on this would also be highly appreciated. Michael -- 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/780e7838-4e01-4716-930d-9503c3d3ef23n%40googlegroups.com.
'Throwable.HasJavaThrowable' has invalid name '?'.
When compiling one of our GWT-based projects with the new GWT 2.10.0 I get: ... [INFO] --- gwt-maven-plugin:2.10.0:compile (default) @ zhstregisterjp-web --- [INFO] Compiling module ch.zh.ksta.zhstregisterjp.ZHStRegisterJPWebDevelopment [INFO]Ignored 5 units with compilation errors in first pass. [INFO] Compile with -strict or with -logLevel set to DEBUG or WARN to see all errors. [INFO]Ignored 14 units with compilation errors in first pass. [INFO] Compile with -strict or with -logLevel set to TRACE or DEBUG to see all errors. [INFO]Errors in com/google/gwt/emul/java/lang/Throwable.java [INFO] [ERROR] Line 344: 'Throwable.HasJavaThrowable' has invalid name '?'. Pardon me? Any hint or direction what I could do or search for here to get over this? -- 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/907f7257-a4af-457e-9f2b-7516e3995afen%40googlegroups.com.
Re: What are legal "user.agent=" values?
For the sake of others running into the same issue: I was able to fix the the above issue causing the error "Value 'ie8' in not a valid value for property 'user.agent'" by providing my own version of the ".../com/sencha/gxt/core/Core.gwt.xml"-file (the original is in gxt-4.0.2.jar) in which I commented away the outdated stuff following the " " comment. But only to now getting stuck with: ... [INFO] --- gwt-maven-plugin:2.10.0:compile (default) @ zhquest-web --- [INFO] Compiling module ch.zh.ksta.zhquest.ZHQuestWebDevelopment [INFO] [ERROR] Unexpected internal compiler error [INFO] java.lang.IllegalArgumentException [INFO] at org.objectweb.asm.ClassVisitor.(Unknown Source) [INFO] at org.objectweb.asm.ClassVisitor.(Unknown Source) [INFO] at com.google.gwt.dev.javac.BytecodeSignatureMaker$CompileDependencyVisitor.(BytecodeSignatureMaker.java:59) [INFO] at com.google.gwt.dev.javac.BytecodeSignatureMaker.visitCompileDependenciesInBytecode(BytecodeSignatureMaker.java:227) [INFO] at com.google.gwt.dev.javac.BytecodeSignatureMaker.getCompileDependencySignature(BytecodeSignatureMaker.java:209) [INFO] at com.google.gwt.dev.javac.CompiledClass.getSignatureHash(CompiledClass.java:166) [INFO] at com.google.gwt.dev.javac.Dependencies$Ref.(Dependencies.java:41) [INFO] at com.google.gwt.dev.javac.Dependencies$Ref.(Dependencies.java:36) [INFO] at com.google.gwt.dev.javac.Dependencies.resolve(Dependencies.java:100) [INFO] at com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater.compile(CompilationStateBuilder.java:349) [INFO] at com.google.gwt.dev.javac.CompilationStateBuilder.doBuildFrom(CompilationStateBuilder.java:532) [INFO] at com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:464) [INFO] at com.google.gwt.dev.cfg.ModuleDef.getCompilationState(ModuleDef.java:423) [INFO] at com.google.gwt.dev.Precompile.precompile(Precompile.java:210) [INFO] at com.google.gwt.dev.Precompile.precompile(Precompile.java:190) [INFO] at com.google.gwt.dev.Precompile.precompile(Precompile.java:131) [INFO] at com.google.gwt.dev.Compiler.compile(Compiler.java:192) [INFO] at com.google.gwt.dev.Compiler.compile(Compiler.java:143) [INFO] at com.google.gwt.dev.Compiler.compile(Compiler.java:132) [INFO] at com.google.gwt.dev.Compiler$1.run(Compiler.java:110) [INFO] at com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java:55) [INFO] at com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRunner.java:50) [INFO] at com.google.gwt.dev.Compiler.main(Compiler.java:113) WTF? On Tuesday, June 28, 2022 at 6:18:07 PM UTC+2 mmo wrote: > Thanks for responding and clarifying this! > > Unfortunately, we are using some library which obviously tries to set an > outdated value and so I now end up in: > ... > [INFO] --- gwt-maven-plugin:2.10.0:compile (default) @ zhquest-web --- > [INFO] Loading inherited module 'ch.zh.ksta.zhquest.ZHQuestWebDevelopment' > [INFO]Loading inherited module 'ch.zh.ksta.zhquest.ZHQuestWeb' > [INFO] Loading inherited module 'com.sencha.gxt.ui.GXT' > [INFO] Loading inherited module 'com.sencha.gxt.data.Data' > [INFO] Loading inherited module 'com.sencha.gxt.core.Core' > [INFO][ERROR] Line 108: Value 'ie8' in not a valid value > for property 'user.agent' > > :-( > > Too many libraries in use here... > > On Monday, June 27, 2022 at 4:58:25 PM UTC+2 Jens wrote: > >> So - according to the release notes which mention “FF”, “Chrome”, “IE” >>> (for IE11), “Edge”, and “Safari” as new user.agent values I changed >>> that to "Chrome, Edge". >>> >> >> Not these values are for running HTMLUnit, not for GWT compiler. >> >> >> Thus my question: what *are* the new valid user.agent values? Do they >>> have to be in all-lowercase (as the old ones) or what exactly can or does >>> one have to enter here? >>> >> >> GWT 2.10.0 user.agent values are >> >>- gecko1_8: Used for FireFox and IE 11 >>- safari: Used for everything based on WebKit (Safari, Chrome, Edge, >>Opera, ...) >> >> >> >> -- 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/44830087-2e16-43a5-8db0-34565876eaa2n%40googlegroups.com.
Re: What are legal "user.agent=" values?
Thanks for responding and clarifying this! Unfortunately, we are using some library which obviously tries to set an outdated value and so I now end up in: ... [INFO] --- gwt-maven-plugin:2.10.0:compile (default) @ zhquest-web --- [INFO] Loading inherited module 'ch.zh.ksta.zhquest.ZHQuestWebDevelopment' [INFO]Loading inherited module 'ch.zh.ksta.zhquest.ZHQuestWeb' [INFO] Loading inherited module 'com.sencha.gxt.ui.GXT' [INFO] Loading inherited module 'com.sencha.gxt.data.Data' [INFO] Loading inherited module 'com.sencha.gxt.core.Core' [INFO][ERROR] Line 108: Value 'ie8' in not a valid value for property 'user.agent' :-( Too many libraries in use here... On Monday, June 27, 2022 at 4:58:25 PM UTC+2 Jens wrote: > So - according to the release notes which mention “FF”, “Chrome”, “IE” >> (for IE11), “Edge”, and “Safari” as new user.agent values I changed that >> to "Chrome, Edge". >> > > Not these values are for running HTMLUnit, not for GWT compiler. > > > Thus my question: what *are* the new valid user.agent values? Do they have >> to be in all-lowercase (as the old ones) or what exactly can or does one >> have to enter here? >> > > GWT 2.10.0 user.agent values are > >- gecko1_8: Used for FireFox and IE 11 >- safari: Used for everything based on WebKit (Safari, Chrome, Edge, >Opera, ...) > > > > -- 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/c1a46cb7-c0ac-48a7-bae5-339f74c1b816n%40googlegroups.com.
Internal Compiler Failure when trying to upgrade a GWT 2.7.0 application to 2.8.1
I am trying to upgrade an application still using GWT 2.7.0 to at least 2.8.1 (and if possible higher, i.e. 2.9.0 or ideally 2.10.0). After raising the GWT version from 2.7.0 to 2.8.1 the compilation of the UI maven module now always ends in an internal compiler failure: ... [INFO] --- gwt-maven-plugin:2.8.1:compile (default) @ zhstregisterjp-web --- [INFO] Compiling module ch.zh.ksta.zhstregisterjp.ZHStRegisterJPWebDevelopment [INFO] [ERROR] An internal compiler exception occurred [INFO] com.google.gwt.dev.jjs.InternalCompilerException: Error constructing Java AST [INFO] at com.google.gwt.dev.jjs.impl.GwtAstBuilder.translateException(GwtAstBuilder.java:3944) [INFO] at com.google.gwt.dev.jjs.impl.GwtAstBuilder.getInternalCompilerException(GwtAstBuilder.java:4351) [INFO] at com.google.gwt.dev.jjs.impl.GwtAstBuilder.createMembers(GwtAstBuilder.java:4043) [INFO] at com.google.gwt.dev.jjs.impl.GwtAstBuilder.processImpl(GwtAstBuilder.java:3883) [INFO] at com.google.gwt.dev.jjs.impl.GwtAstBuilder.process(GwtAstBuilder.java:3918) [INFO] at com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater$UnitProcessorImpl.process(CompilationStateBuilder.java:129) [INFO] at com.google.gwt.dev.javac.JdtCompiler$CompilerImpl.process(JdtCompiler.java:384) [INFO] at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:470) [INFO] at com.google.gwt.dev.javac.JdtCompiler.doCompile(JdtCompiler.java:1092) [INFO] at com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater.compile(CompilationStateBuilder.java:325) [INFO] at com.google.gwt.dev.javac.CompilationStateBuilder.doBuildFrom(CompilationStateBuilder.java:548) [INFO] at com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:479) [INFO] at com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:465) [INFO] at com.google.gwt.dev.cfg.ModuleDef.getCompilationState(ModuleDef.java:423) [INFO] at com.google.gwt.dev.Precompile.precompile(Precompile.java:222) [INFO] at com.google.gwt.dev.Precompile.precompile(Precompile.java:202) [INFO] at com.google.gwt.dev.Precompile.precompile(Precompile.java:143) [INFO] at com.google.gwt.dev.Compiler.compile(Compiler.java:204) [INFO] at com.google.gwt.dev.Compiler.compile(Compiler.java:155) [INFO] at com.google.gwt.dev.Compiler.compile(Compiler.java:144) [INFO] at com.google.gwt.dev.Compiler$1.run(Compiler.java:118) [INFO] at com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java:55) [INFO] at com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRunner.java:50) [INFO] at com.google.gwt.dev.Compiler.main(Compiler.java:125) [INFO] Caused by: java.lang.NoSuchMethodError: org.eclipse.jdt.internal.compiler.lookup.MethodBinding.isDefaultMethod()Z [INFO] at com.google.gwt.dev.jjs.impl.GwtAstBuilder.createMethod(GwtAstBuilder.java:4138) [INFO] at com.google.gwt.dev.jjs.impl.GwtAstBuilder.createMembers(GwtAstBuilder.java:4033) [INFO] ... 21 more [INFO][ERROR] at ClickEvent.java(23): public class ClickEvent extends MouseEvent [INFO] org.eclipse.jdt.internal.compiler.ast.TypeDeclaration --- ANY idea or hint anyone, how to analyze this? Or how to figure out what could be causing this and where to start searching??? -- 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/b76c64eb-ea0e-479e-a7c4-8f4db3f389d5n%40googlegroups.com.
What are legal "user.agent=" values?
I was trying to update our application from GWT 2.8.1 to the new GWT 2.10.0. The first compilation failed with the eror message that ie10 was not a legal user.agent value (we had indeed used that value, since it was the newest IE version available). So - according to the release notes which mention “FF”, “Chrome”, “IE” (for IE11), “Edge”, and “Safari” as new user.agent values I changed that to "Chrome, Edge". The subsequent compilation then succeeded but when starting up the application I get the error: [INFO] [ERROR] Line 21: Value 'Chrome' in not a valid value for property 'user.agent' [INFO] [ERROR] Line 21: Value 'Edge' in not a valid value for property 'user.agent' Thus my question: what *are* the new valid user.agent values? Do they have to be in all-lowercase (as the old ones) or what exactly can or does one have to enter here? -- 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/d3714e65-92f8-47f3-968a-892cb0baad01n%40googlegroups.com.
Re: Upgrading from 2.8.1 to 2.9.0 yields "...type not found, or there are compile errors..."?!?
Hi and thanks for responding. We will double-check in that direction
although I have doubts that this is the issue, because this has worked fine
with the previous version, i.e. with v2.8.1 the compiler obviously *did*
find the files. Has v2.9.0 a different or more rigid search strategy?
On Tuesday, December 7, 2021 at 12:26:11 AM UTC+1 robn...@gmail.com wrote:
> It looks like the GWT compiler cannot find the source .java file for that
> class, which it will need. Perhaps it is in a directory that is not
> covered by the tag in your module.gwt.xml file?
>
> On Tuesday, December 7, 2021 at 3:02:09 AM UTC+11 mmo wrote:
>
>> We are trying to migrate a GWT application that is running fine with GWT
>> 2.8.1 to GWT 2.9.0.
>> When we do a gwt:run the usual Jetty dialog comes up and without errors
>> nor exceptions and comes to the point where it offers to copy the URL or
>> launch the default browser.
>>
>> When we copy/paste the URL to the browser we get a ""Compiling SSt"
>> message and then the browser hangs ("SSt" is the name of the application).
>>
>> On the console we get the output:
>> ...
>> GET /recompile/sstweb
>>Job ch.zh.ksta.sst.SstWebDevelopment_1_2
>> starting job: ch.zh.ksta.sst.SstWebDevelopment_1_2
>> binding: gxt.device=desktop
>> binding: gxt.user.agent=ie11
>> binding: user.agent=gecko1_8
>> binding: user.agent.os=windows
>> Compiling module ch.zh.ksta.sst.SstWebDevelopment
>> Ignored 20 units with compilation errors in first pass.
>> Compile with -strict or with -logLevel set to TRACE or DEBUG to see all
>> errors.
>> Computing all possible rebind results for
>> 'com.gwtplatform.mvp.client.ApplicationController'
>> Rebinding com.gwtplatform.mvp.client.ApplicationController
>>Invoking generator
>> com.gwtplatform.mvp.rebind.ApplicationControllerGenerator
>> [ERROR] The type
>> 'ch.zh.ksta.sst.client.SstBootstrapper' was not found, either the class
>> name is wrong or there are compile errors in your code.
>> [ERROR] The type
>> 'ch.zh.ksta.sst.client.SstBootstrapper' was not found, either the class
>> name is wrong or there are compile errors in your code.
>> [ERROR] There was a problem generating the
>> ApplicationController, this can be caused by bad GWT module configuration
>> or compile errors in your source code.
>> [WARN] For the following type(s), generated source was never
>> committed (did you forget to call commit()?)
>> [WARN] com.gwtplatform.mvp.client.ApplicationControllerImpl
>> Unification traversed 29116 fields and methods and 2736 types.
>> 2699 are considered part of the current module and 2699 had all of their
>> fields and methods traversed.
>> Compiling 1 permutation
>> Compiling permutation 0...
>> Linking per-type JS with 2678 new/changed types.
>> Source Maps Enabled
>> Compile of permutations succeeded
>> Compilation succeeded -- 6,609s
>> ...
>>
>> We don't understand why the client boots trapper class is not found
>> (assuming the message is correct). It *is* contained in both, the classes
>> folder as well as in the generated .war file and the class' name is
>> correct. We also don't see any compile errors in the code (at least
>> IntelliJ doesn't display any...).
>> Any idea or hint, what might be wrong here? Or in which direction we
>> could search?
>> Or any info that might be helpful here to pinpoint this issue?
>>
>
--
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/088dce7f-05d1-4d2f-81bd-701fb1c27ac6n%40googlegroups.com.
Re: Upgrading from 2.8.1 to 2.9.0 yields "...type not found, or there are compile errors..."?!?
I forgot to mention: this is using Java 1.8 (AdoptOpenJDK -
jdk-8.0.292.10-hotspot).
On Monday, December 6, 2021 at 5:02:09 PM UTC+1 mmo wrote:
> We are trying to migrate a GWT application that is running fine with GWT
> 2.8.1 to GWT 2.9.0.
> When we do a gwt:run the usual Jetty dialog comes up and without errors
> nor exceptions and comes to the point where it offers to copy the URL or
> launch the default browser.
>
> When we copy/paste the URL to the browser we get a ""Compiling SSt"
> message and then the browser hangs ("SSt" is the name of the application).
>
> On the console we get the output:
> ...
> GET /recompile/sstweb
>Job ch.zh.ksta.sst.SstWebDevelopment_1_2
> starting job: ch.zh.ksta.sst.SstWebDevelopment_1_2
> binding: gxt.device=desktop
> binding: gxt.user.agent=ie11
> binding: user.agent=gecko1_8
> binding: user.agent.os=windows
> Compiling module ch.zh.ksta.sst.SstWebDevelopment
> Ignored 20 units with compilation errors in first pass.
> Compile with -strict or with -logLevel set to TRACE or DEBUG to see all
> errors.
> Computing all possible rebind results for
> 'com.gwtplatform.mvp.client.ApplicationController'
> Rebinding com.gwtplatform.mvp.client.ApplicationController
>Invoking generator
> com.gwtplatform.mvp.rebind.ApplicationControllerGenerator
> [ERROR] The type 'ch.zh.ksta.sst.client.SstBootstrapper'
> was not found, either the class name is wrong or there are compile errors
> in your code.
> [ERROR] The type 'ch.zh.ksta.sst.client.SstBootstrapper'
> was not found, either the class name is wrong or there are compile errors
> in your code.
> [ERROR] There was a problem generating the
> ApplicationController, this can be caused by bad GWT module configuration
> or compile errors in your source code.
> [WARN] For the following type(s), generated source was never
> committed (did you forget to call commit()?)
> [WARN] com.gwtplatform.mvp.client.ApplicationControllerImpl
> Unification traversed 29116 fields and methods and 2736 types.
> 2699 are considered part of the current module and 2699 had all of their
> fields and methods traversed.
> Compiling 1 permutation
> Compiling permutation 0...
> Linking per-type JS with 2678 new/changed types.
> Source Maps Enabled
> Compile of permutations succeeded
> Compilation succeeded -- 6,609s
> ...
>
> We don't understand why the client boots trapper class is not found
> (assuming the message is correct). It *is* contained in both, the classes
> folder as well as in the generated .war file and the class' name is
> correct. We also don't see any compile errors in the code (at least
> IntelliJ doesn't display any...).
> Any idea or hint, what might be wrong here? Or in which direction we could
> search?
> Or any info that might be helpful here to pinpoint this issue?
>
--
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/b1b463f2-2e4f-46ee-986d-0cc944f7e85fn%40googlegroups.com.
Upgrading from 2.8.1 to 2.9.0 yields "...type not found, or there are compile errors..."?!?
We are trying to migrate a GWT application that is running fine with GWT
2.8.1 to GWT 2.9.0.
When we do a gwt:run the usual Jetty dialog comes up and without errors nor
exceptions and comes to the point where it offers to copy the URL or launch
the default browser.
When we copy/paste the URL to the browser we get a ""Compiling SSt" message
and then the browser hangs ("SSt" is the name of the application).
On the console we get the output:
...
GET /recompile/sstweb
Job ch.zh.ksta.sst.SstWebDevelopment_1_2
starting job: ch.zh.ksta.sst.SstWebDevelopment_1_2
binding: gxt.device=desktop
binding: gxt.user.agent=ie11
binding: user.agent=gecko1_8
binding: user.agent.os=windows
Compiling module ch.zh.ksta.sst.SstWebDevelopment
Ignored 20 units with compilation errors in first pass.
Compile with -strict or with -logLevel set to TRACE or DEBUG to see all
errors.
Computing all possible rebind results for
'com.gwtplatform.mvp.client.ApplicationController'
Rebinding com.gwtplatform.mvp.client.ApplicationController
Invoking generator
com.gwtplatform.mvp.rebind.ApplicationControllerGenerator
[ERROR] The type 'ch.zh.ksta.sst.client.SstBootstrapper'
was not found, either the class name is wrong or there are compile errors
in your code.
[ERROR] The type 'ch.zh.ksta.sst.client.SstBootstrapper'
was not found, either the class name is wrong or there are compile errors
in your code.
[ERROR] There was a problem generating the
ApplicationController, this can be caused by bad GWT module configuration
or compile errors in your source code.
[WARN] For the following type(s), generated source was never
committed (did you forget to call commit()?)
[WARN] com.gwtplatform.mvp.client.ApplicationControllerImpl
Unification traversed 29116 fields and methods and 2736 types.
2699 are considered part of the current module and 2699 had all of their
fields and methods traversed.
Compiling 1 permutation
Compiling permutation 0...
Linking per-type JS with 2678 new/changed types.
Source Maps Enabled
Compile of permutations succeeded
Compilation succeeded -- 6,609s
...
We don't understand why the client boots trapper class is not found
(assuming the message is correct). It *is* contained in both, the classes
folder as well as in the generated .war file and the class' name is
correct. We also don't see any compile errors in the code (at least
IntelliJ doesn't display any...).
Any idea or hint, what might be wrong here? Or in which direction we could
search?
Or any info that might be helpful here to pinpoint this issue?
--
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/ead73d56-2ed7-43da-9d57-4d0c50be6f18n%40googlegroups.com.
Re: What setting controls whether Eclipse is building the development version or not?
Issue solved! Probably due to my experimenting (among them the re-creation of a Server-definition) the CodeServer's launcherDir-path ( \.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps\rwtool-web) and the WTP deploy-path for Tomcat: (- Dwtp.deploy="U:\Documents\eclipse\workspace_KStA_RW-Tool\.metadata\.plugins\org.eclipse.wst.server.core\tmp1\wtpwebapps) had diverged from each other (Note the "tmp0" vs. "tmp1" in the paths). Once I had realized and fixed this, everything came back to normal! Apologies for the bandwidth used... On Tuesday, August 24, 2021 at 4:02:32 PM UTC+2 mmo wrote: > I somehow destroyed my Eclipse setup for GWT applicaiton debugging - could > some kind soul please help me to get going again? > > Before I had set up my GWT project using a local Tomcat server such that I > was able to run and debug it using: > > First starting the CodeServer (via right-click on the GWT project --> "Run > As" --> "GWT Development Mode") on localhost:9876. > Second: starting Tomcat (via right-click on the GWT project --> "Run As" > --> "Run on Server") on localhost:8080 > > This had worked out-of-the-box and created and started up the application > in development mode where it fetches the .nocache.js code from the > code server, but directs all HTML, CSS and especially also all RPC-requests > to Tomcat's application port. With that I had been able to start, > breakpoint and debug my GWT application (though the server side code only). > > Trying to get this setup to also provide the sourcemaps and allow me to > debug also client side code using Chrome and the SDBG plugin I somehow > destroyed that working setup and I haven't understood, yet, why this is not > working anymore: > > While I can still start the code server as described above starting up the > application on Tomcat downloads an index.html file-version that tries to > fetch the .nocache.js file from Tomcat as well (i.e. using the URL > in > the index.html-file). > > That of course doesn't work (that file needs to be fetched from the > code-server's port!) and so my GWT applications (or rather its welcome > page) just hangs and nothing happens. > > I have no clue what I did or destroyed or disabled so that this doesn't > work anymore. > What do I need to do to convince Eclipse to build the development version > again like it used to? > > -- 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/c25e0099-4aea-4ed8-9d86-88ea2b614a09n%40googlegroups.com.
Re: Trying to get GWT app deployed in local Tomcat (using Eclipse)
Really odd! Here is how this looks on my side: [image: GWT-Facet-Settings.png] On Tuesday, August 24, 2021 at 3:41:34 PM UTC+2 Craig Mitchell wrote: > Interesting. I don't have that setting: > > [image: screenshot.png] > > I'm using the standard Eclipse for Java Developers. Not Eclipse for > Enterprise Java. > > On Monday, 23 August 2021 at 11:01:20 pm UTC+10 mmo wrote: > >> @Craig Mitchell >> >> > I've never seen an option to start the code server automatically >> Right-click on the mode --> GTW --> Settings --> GWT - Facet Settings: >> There is a checkbox under "Super Development Mode" labeled "Sync the >> CodeServer state with the WTP server. The WTP server start and stop will >> also start and stop the CodeServer". >> >> > I think you mean the CodeServer doesn't always show in the Development >> mode. >> No - as I wrote: the CodeServer shows up reliably in this view, but the >> Web-Server doesn't anymore. It used to, though, so I am puzzled why this is >> not working anymore. >> >> > I just use a "Launch Chrome" launcher to start Chrome in debug, so I >> don't need it to show up. >> These "Connect to Chrome" and "Launch Chrome" entries usually appear in >> the "Run As"/"Debug As"-context menu but often they don't. And once they >> disappeared, they don't show up anymore until the next Eclipse-restart. >> Very odd and annoying! :-( >> >> -- 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/b0aa2da4-dd56-4e56-8856-6d511b7c568dn%40googlegroups.com.
What setting controls whether Eclipse is building the development version or not?
I somehow destroyed my Eclipse setup for GWT applicaiton debugging - could some kind soul please help me to get going again? Before I had set up my GWT project using a local Tomcat server such that I was able to run and debug it using: First starting the CodeServer (via right-click on the GWT project --> "Run As" --> "GWT Development Mode") on localhost:9876. Second: starting Tomcat (via right-click on the GWT project --> "Run As" --> "Run on Server") on localhost:8080 This had worked out-of-the-box and created and started up the application in development mode where it fetches the .nocache.js code from the code server, but directs all HTML, CSS and especially also all RPC-requests to Tomcat's application port. With that I had been able to start, breakpoint and debug my GWT application (though the server side code only). Trying to get this setup to also provide the sourcemaps and allow me to debug also client side code using Chrome and the SDBG plugin I somehow destroyed that working setup and I haven't understood, yet, why this is not working anymore: While I can still start the code server as described above starting up the application on Tomcat downloads an index.html file-version that tries to fetch the .nocache.js file from Tomcat as well (i.e. using the URL in the index.html-file). That of course doesn't work (that file needs to be fetched from the code-server's port!) and so my GWT applications (or rather its welcome page) just hangs and nothing happens. I have no clue what I did or destroyed or disabled so that this doesn't work anymore. What do I need to do to convince Eclipse to build the development version again like it used to? -- 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/d986be1c-0931-459b-845e-f44547ac3e35n%40googlegroups.com.
Re: Trying to get GWT app deployed in local Tomcat (using Eclipse)
@Craig Mitchell > I've never seen an option to start the code server automatically Right-click on the mode --> GTW --> Settings --> GWT - Facet Settings: There is a checkbox under "Super Development Mode" labeled "Sync the CodeServer state with the WTP server. The WTP server start and stop will also start and stop the CodeServer". > I think you mean the CodeServer doesn't always show in the Development mode. No - as I wrote: the CodeServer shows up reliably in this view, but the Web-Server doesn't anymore. It used to, though, so I am puzzled why this is not working anymore. > I just use a "Launch Chrome" launcher to start Chrome in debug, so I don't need it to show up. These "Connect to Chrome" and "Launch Chrome" entries usually appear in the "Run As"/"Debug As"-context menu but often they don't. And once they disappeared, they don't show up anymore until the next Eclipse-restart. Very odd and annoying! :-( -- 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/a45eed60-1a6a-47a7-88a7-cb815c2b62d6n%40googlegroups.com.
Re: Trying to get GWT app deployed in local Tomcat (using Eclipse)
Thanks all! Meanwhile I got this starting up nicely from inside eclipse and - boy - this is really much faster! Things that don't work, yet: 1. As far as I understand, the CodeServer should be started up automatically when starting the WebServer. There even is a flag in the GWT settings "Sync the CodeServer state with the WTP server. The WTP server start and stop will also start and stop the CodeServer". That is not working for me. I always have to start the CodeServer separately. Strange enough it sometimes gets stopped, when I stop Tomcat, but it is never started, when I start Tomcat. So this feature seems to work only in one direction and then unreliably. But fortunately that's not such a big deal... 2. The CodeServer reliably appears with its URL in the "Development Mode"-view of the GWT plugin. However, the Tomcat server does so not always. Sometimes it appears, sometimes it does not. And right now it seems to refuse altogether. I have started and restarted it maybe 10 times now but its URL does not show up in that view. Any idea what setting or state could influence that? The issue with the Web-server's URL not being listed there is, that I then can not right-click on the URL and choose to "Run with SDBG Chrome JS debugger". I would like to try that mode to see if that's working and helpful to debug client code. Any advice on these topics? On Sunday, August 8, 2021 at 6:23:05 PM UTC+2 vas...@gmail.com wrote: > So maybe it is possible for you to skip GWT compilation while building the >> *.war directory to save some minutes. > > > In my case this is a huge understatement. In superdevmode the compilation > is nearly instant (1-2secs maybe less) instead of 90sec of the full > compile. > > I don't know how it behaves in really big codebases that take several > minutes to compile but I bet it would make a big difference. > > So follow Jens' advice and try to setup superdevmode for development. For > production you still need the final compilation step. > > The other solution is to use code splitting > http://www.gwtproject.org/doc/latest/DevGuideCodeSplitting.html but a) I > have never done it and b) certainly looks more invasing. > -- > Vassilis Virvilis > -- 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/4ab7dc92-c053-4d2e-8140-e1dd2605962an%40googlegroups.com.
Re: The GWT Eclipse Plugin stopped working in Eclipse 2021-06
Now that's odd! Just out of curiosity I installed the plugin a 3rd time on my initial Eclipse instance (I wanted to see the exact exception stack trace hoping that this might give me a clue) and this time everything kept working fine! No more issue or interference with the Git view! Amazing! Keeping fingers crossed things stay like this... Well, now I can finally continue on what I actually had intended to do: debug our GWT client problem. :-/ Thanks again for your detailed instructions re. the plugin again! On Friday, August 20, 2021 at 2:48:54 PM UTC+2 Craig Mitchell wrote: > I've not seen the error. 2021-06, connecting to a Bitbucket repos. > > On Friday, 20 August 2021 at 8:39:27 pm UTC+10 Shawn wrote: > >> Ha funny or not after a little use I got the same error. >> >> I couldn't find the underlying issue mentioned anywhere (was a missing >> class) so didn't know what to reinstall and just restarted eclipse. It >> works again. >> >> On Fri, Aug 20, 2021 at 5:57 PM Shawn Brown >> wrote: >> >>> Hey. Sorry to hear that. >>> >>> I'm on v2021-06 and don't see eGit crashing. That said, I mostly use >>> GitHub Desktop. >>> >>> I do remember struggling with v2021-03 to get a compatible eGit version >>> installed. Not sure why that was or if it's related to the SDBG plugin, >>> but I think I installed the SDBG plugin prior to v2021-03. Likely it was >>> some other update or installation I tried that required a newer version of >>> eGit and that installing it perhaps resolved the issue with SDBG. Just >>> speculation here... >>> >>> On Fri, Aug 20, 2021 at 5:04 PM mmo wrote: >>> >>>> @Craig Mitchell >>>> > ... >>>> > And all working great now! Yay! Thanks. >>>> >>>> Unfortunately not quite: >>>> >>>> While the instructions to download, build and replace the SDBG plugin >>>> *do* work fine the replacement of the plugin had a *very *adverse >>>> side-effect (on my eclipse at least - v2021-03): >>>> With the new SDBG plugin installed the eGit-plugin reproducibly >>>> crashes. I.e. I then can not access any git-repo anymore using Eclipse. >>>> >>>> Cheers, >>>> Michael >>>> >>>> -- >>>> 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-tool...@googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/google-web-toolkit/6cdd59cb--46a7-845f-8e42f5833420n%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/google-web-toolkit/6cdd59cb--46a7-845f-8e42f5833420n%40googlegroups.com?utm_medium=email_source=footer> >>>> . >>>> >>> -- 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/e3c860ce-c969-4a42-94ed-70cded2a19afn%40googlegroups.com.
Re: The GWT Eclipse Plugin stopped working in Eclipse 2021-06
I experimented further and installed the very same plugin in a second instance of Eclipse (same version) and here it did not do any noticeable harm. I haven't tested whether it actually works but at least it caused no trouble with the Git view. I guess my next step will be to clone that second eclipse instance and replace my first one. Thanks for pointing out that you hadn't seen any such issue - this kept me going! On Friday, August 20, 2021 at 2:48:54 PM UTC+2 Craig Mitchell wrote: > I've not seen the error. 2021-06, connecting to a Bitbucket repos. > > On Friday, 20 August 2021 at 8:39:27 pm UTC+10 Shawn wrote: > >> Ha funny or not after a little use I got the same error. >> >> I couldn't find the underlying issue mentioned anywhere (was a missing >> class) so didn't know what to reinstall and just restarted eclipse. It >> works again. >> >> On Fri, Aug 20, 2021 at 5:57 PM Shawn Brown >> wrote: >> >>> Hey. Sorry to hear that. >>> >>> I'm on v2021-06 and don't see eGit crashing. That said, I mostly use >>> GitHub Desktop. >>> >>> I do remember struggling with v2021-03 to get a compatible eGit version >>> installed. Not sure why that was or if it's related to the SDBG plugin, >>> but I think I installed the SDBG plugin prior to v2021-03. Likely it was >>> some other update or installation I tried that required a newer version of >>> eGit and that installing it perhaps resolved the issue with SDBG. Just >>> speculation here... >>> >>> On Fri, Aug 20, 2021 at 5:04 PM mmo wrote: >>> >>>> @Craig Mitchell >>>> > ... >>>> > And all working great now! Yay! Thanks. >>>> >>>> Unfortunately not quite: >>>> >>>> While the instructions to download, build and replace the SDBG plugin >>>> *do* work fine the replacement of the plugin had a *very *adverse >>>> side-effect (on my eclipse at least - v2021-03): >>>> With the new SDBG plugin installed the eGit-plugin reproducibly >>>> crashes. I.e. I then can not access any git-repo anymore using Eclipse. >>>> >>>> Cheers, >>>> Michael >>>> >>>> -- >>>> 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-tool...@googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/google-web-toolkit/6cdd59cb--46a7-845f-8e42f5833420n%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/google-web-toolkit/6cdd59cb--46a7-845f-8e42f5833420n%40googlegroups.com?utm_medium=email_source=footer> >>>> . >>>> >>> -- 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/4d623bd3-55ec-4601-b49e-688fa08cf58dn%40googlegroups.com.
Re: The GWT Eclipse Plugin stopped working in Eclipse 2021-06
Unfortunately, just restarting eclipse hadn't fixed it. It kept crashing when opening the Git Repo view. Only after uninstalling the (new) SDBG plugin the Git Repo view worked again. I actually retried and re-installed the plugin a second time and got these crashes again. Then un-installed it a again and Git working again. Only then I reported here. Will try again one I installed a newer eclipse version. On Friday, August 20, 2021 at 12:39:27 PM UTC+2 Shawn wrote: > Ha funny or not after a little use I got the same error. > > I couldn't find the underlying issue mentioned anywhere (was a missing > class) so didn't know what to reinstall and just restarted eclipse. It > works again. > > On Fri, Aug 20, 2021 at 5:57 PM Shawn Brown wrote: > >> Hey. Sorry to hear that. >> >> I'm on v2021-06 and don't see eGit crashing. That said, I mostly use >> GitHub Desktop. >> >> I do remember struggling with v2021-03 to get a compatible eGit version >> installed. Not sure why that was or if it's related to the SDBG plugin, >> but I think I installed the SDBG plugin prior to v2021-03. Likely it was >> some other update or installation I tried that required a newer version of >> eGit and that installing it perhaps resolved the issue with SDBG. Just >> speculation here... >> >> On Fri, Aug 20, 2021 at 5:04 PM mmo wrote: >> >>> @Craig Mitchell >>> > ... >>> > And all working great now! Yay! Thanks. >>> >>> Unfortunately not quite: >>> >>> While the instructions to download, build and replace the SDBG plugin >>> *do* work fine the replacement of the plugin had a *very *adverse >>> side-effect (on my eclipse at least - v2021-03): >>> With the new SDBG plugin installed the eGit-plugin reproducibly crashes. >>> I.e. I then can not access any git-repo anymore using Eclipse. >>> >>> Cheers, >>> Michael >>> >>> -- >>> 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-tool...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/google-web-toolkit/6cdd59cb--46a7-845f-8e42f5833420n%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/google-web-toolkit/6cdd59cb--46a7-845f-8e42f5833420n%40googlegroups.com?utm_medium=email_source=footer> >>> . >>> >> -- 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/853cea8d-4760-4eba-a2f2-d0771daa7ce7n%40googlegroups.com.
Re: The GWT Eclipse Plugin stopped working in Eclipse 2021-06
@Craig Mitchell > ... > And all working great now! Yay! Thanks. Unfortunately not quite: While the instructions to download, build and replace the SDBG plugin *do* work fine the replacement of the plugin had a *very *adverse side-effect (on my eclipse at least - v2021-03): With the new SDBG plugin installed the eGit-plugin reproducibly crashes. I.e. I then can not access any git-repo anymore using Eclipse. Cheers, Michael -- 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/6cdd59cb--46a7-845f-8e42f5833420n%40googlegroups.com.
Re: The GWT Eclipse Plugin stopped working in Eclipse 2021-06
@Craig Mitchell > ... > And all working great now! Yay! Thanks. While the instructions to download, build and replace the SDBG plugin *do* work file the replacement of the plugin had a very adverse side-effect (on my eclipse at least - v2021-03): With the new SDBG plugin installed the eGit-plugin reproducibly crashes. I.e. I then can not access any git-repo anymore using Eclipse. The installation of the plugin went smoothly and showed no conflict or warning but when starting eclipse and opening the Git-Repositories view (or switching to the Git perspective with that view open) crashes. Anybody else also experiencing this? Any known fix or work-around? -- 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/0bc79865-871b-427b-a4ea-1a08eb9903a9n%40googlegroups.com.
Trying to get GWT app deployed in local Tomcat (using Eclipse)
I am (trying to) upgrade our GWT-based legacy application to use newer Hibernate, Spring and other library versions. After some (substantial) pull-ups this works mostly fine by now when deploying a fully generated and packaged .war file, but building this thing always takes forever and day (the infamous permutations and other steps...). Since the Jetty that's built into the GWT plugin has issues with newer (multi-release) .jar files (see my different discussion) I had to switch deployment of the application to Tomcat (which is our target server anyway) also for development. To speed up the development cycle I am thus trying to get this thing also to run as unpacked file using Eclipse's Tomcat "server bridge". This plugin deploys a web application to a temporary directory in the eclipse workspace and then starts Tomcat passing it the proper settings using VM options like: -Dcatalina.base="\.metadata\.plugins\org.eclipse.wst.server.core\tmp0" -Dcatalina.home="C:\Program Files\Apache Software Foundation\Tomcat 8.5" -Dwtp.deploy="\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps" . With that the application begins to start up, I get to the point where I login and get the initial index.html page but as soon as some GWT-generated Java-script has to be loaded things stall. As I had to learn the entire GWT generated code which - as I found out - gets compiled into directories named like C :\Users\\AppData\Local\Temp\gwt-codeserver-8682038074388630768.tmp\.WebWar\compile-1\war\ is *not* copied over or linked into the wtpwebapps directory. I experimented a bit and if one creates a Junction (a kind of soft-link in Windows) in the wtpwebapps\ directory pointing to that generated GWT code then the application indeed starts loading the UI. However, at some point it invariably dies with a popup that it couldn't load the application from Super Dev Mode Server at http://localhost:9876. So there are (at least) two things missing: the GWT code has to be hooked or copied into the generated server configuration and apparently there must also be a Dev Server available. At this point - since I don't understand this (Super) Dev Mode well enough - I decided to ask in this forum: Has anyone got this working so that one can deploy a GWT application to a local Tomcat instance without first having to pack everything up and deploy as a .war file, so that one can essentially continue to run and debug as one used to using Jetty before using the maven goals gwt:run or gwt:debug? Is that described or documented anywhere? Or would some kind soul mind to share his/her knowledge on how to get this working? It doesn't have to be for Eclipse - IntelliJ would be ok as well. The point is that it should not require the lengthy build-package-deploy cycle because a cycle-time of >10 minutes is just unbearable for development. Any suggestions welcome! -- 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/defb3a0d-7dd0-43b1-ac6c-ae4ca179126fn%40googlegroups.com.
Trying to get GWT app deployed in local Tomcat using Eclipse
I am (trying to) upgrade our GWT-based legacy application to use newer Hibernate, Spring and other library versions. After some (substantial) pull-ups this works mostly fine by now when deploying a fully generated and packaged .war file, but building this thing always takes forever and day (the infamous permutations and other steps...). Since the Jetty that's built into the GWT plugin has issues with newer (multi-release) .jar files (see my different discussion) I had to switch deployment of the application to Tomcat (which is our target server anyway) also for development. To speed up the development cycle I am thus trying to get this thing also to run as unpacked file using Eclipse's Tomcat "server bridge". This plugin deploys a web application to a temporary directory in the eclipse workspace and then starts Tomcat passing it the proper settings using VM options like: -Dcatalina.base="\.metadata\.plugins\org.eclipse.wst.server.core\tmp0" -Dcatalina.home="C:\Program Files\Apache Software Foundation\Tomcat 8.5" -Dwtp.deploy=" \.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps". With that application begins to start up, I get to the point where I login and get the initial index.html page but as soon as some GWT-generated Java-script has to be loaded things stall. As I had to learn the entire GWT generated code which - as I found out - gets compiled into directories named like C:\Users\\AppData\Local\Temp\gwt-codeserver-8682038074388630768.tmp\.WebWar\compile-1\war\ is *not* copied over or linked into the wtpwebapps directory. I experimented a bit and if one creates a Junction (a kind of soft-link in Windows) in the wtpwebapps\ directory pointing to that generated GWT code then the application indeed starts loading the UI. However, at some point it invariably dies with a popup that it couldn't load the application from Super Dev Mode Server at http://localhost:9876. So there are (at least) two things missing: the GWT code has to be hooked or copied into the generated server configuration and apparently there must also be a Dev Server available. At this point - since I don't understand this (Super) Dev Mode well enough - I decided to ask in this forum: Has anyone got this working so that one can deploy a GWT application to a local Tomcat instance without first having to pack everything up and deploy as a .war file, so that one can essentially continue to run and debug as one used to using Jetty before using the maven goals gwt:run or gwt:debug? Is that described or documented anywhere? Or would some kind soul mind to share his/her knowledge on how to get this working? It doesn't have to be for Eclipse - IntelliJ would be ok as well. The point is that it should not require the lengthy build-package-deploy cycle because a cycle-time of >10 minutes is just unbearable for development. Any suggestions welcome! -- 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/ebb1a859-535c-41ea-b8c8-a9d5f4b38123n%40googlegroups.com.
Re: Frequent Java runtime crashes when compiling GWT code
On Thursday, August 5, 2021 at 6:14:25 PM UTC+2 m.conr...@gmail.com wrote: > Can you try testing with adoptopenjdk? > > I've had issues with stock openjdk before with odd crashes that don't > happen with adoptopenjdk. > I *am* using AdoptOpenJDK (jdk8u292-b10 ) -- 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/be7a6b23-6b40-4d07-8864-c51603002a5bn%40googlegroups.com.
Frequent Java runtime crashes when compiling GWT code
We are seeing frequent Java runtime crashes (and I *really* mean often: about 2 in 3 compilations crash) while building our GWT-based application. I haven't been able to figure out, precisely *what* is triggering this (see the log-snippet below). It happens more or less right at the beginning of that goal and from what I read there it seems to be in the Maven plugin that jars up our module with the GWT stuff in it. Are others seeing this or similar Java runtime crashes as well? I recently upgraded the JDK that our CI-environment is using (we are bound to Java-8 for the time being) hoping this would improve the situation, but its still the same and it getting mighty tedious! Any ideas or suggestions? Just in case: it's NOT a HW-issue! The build environment is running in an OpenShift-based virtual environment and these crashes happen for *this* project only. We have other GWT-based applications and these build fine in the same environment. I have seen similar crashes before (but really *very* seldom only). But with *this* projects it's getting out-of-hand lately. ... 16:57:22 [INFO] 16:57:22 [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ module-gwt-jar --- 16:57:22 *** Error in `/tmp/tools/hudson.model.JDK/jdk8u292/jdk8u292-b10/bin/java': realloc(): invalid next size: 0x7fabb8829570 *** 16:57:22 *** Error in `/tmp/tools/hudson.model.JDK/jdk8u292/jdk8u292-b10/bin/java': realloc(): invalid next size: 0x7fabb8829570 *** 16:57:22 === Backtrace: = 16:57:22 === Backtrace: = 16:57:22 /lib64/libc.so.6(+0x7f474)[0x7fac2976c474] 16:57:22 /lib64/libc.so.6(+0x7f474)[0x7fac2976c474] 16:57:22 /lib64/libc.so.6(+0x84861)[0x7fac29771861] 16:57:22 /lib64/libc.so.6(+0x84861)[0x7fac29771861] 16:57:22 /lib64/libc.so.6(realloc+0x1d2)[0x7fac29772e12] 16:57:22 /lib64/libc.so.6(realloc+0x1d2)[0x7fac29772e12] 16:57:22 /lib64/libnss_wrapper.so(+0x388f)[0x7fac2a0f688f] 16:57:22 /lib64/libnss_wrapper.so(+0x388f)[0x7fac2a0f688f] 16:57:22 /lib64/libnss_wrapper.so(+0x58e9)[0x7fac2a0f88e9] 16:57:22 /lib64/libnss_wrapper.so(+0x58e9)[0x7fac2a0f88e9] 16:57:22 /lib64/libnss_wrapper.so(+0x5dcd)[0x7fac2a0f8dcd] 16:57:22 /lib64/libnss_wrapper.so(+0x5dcd)[0x7fac2a0f8dcd] 16:57:22 /lib64/libnss_wrapper.so(+0x5edb)[0x7fac2a0f8edb] 16:57:22 /lib64/libnss_wrapper.so(+0x5edb)[0x7fac2a0f8edb] 16:57:22 /lib64/libnss_wrapper.so(getgrgid_r+0x59)[0x7fac2a0fac99] 16:57:22 /lib64/libnss_wrapper.so(getgrgid_r+0x59)[0x7fac2a0fac99] 16:57:22 /tmp/tools/hudson.model.JDK/jdk8u292/jdk8u292-b10/jre/lib/amd64/libnio.so(Java_sun_nio_fs_UnixNativeDispatcher_getgrgid+0x8e)[0x7fac0b7f529e] 16:57:22 /tmp/tools/hudson.model.JDK/jdk8u292/jdk8u292-b10/jre/lib/amd64/libnio.so(Java_sun_nio_fs_UnixNativeDispatcher_getgrgid+0x8e)[0x7fac0b7f529e] 16:57:22 [0x7fac149c0087] 16:57:22 [0x7fac149c0087] 16:57:22 === Memory map: 16:57:22 === Memory map: 16:57:22 e000-e3f0 rw-p 00:00 0 16:57:22 e3f0-f558 ---p 00:00 0 16:57:22 f558-1 rw-p 00:00 0 16:57:22 1-10036 rw-p 00:00 0 16:57:22 10036-14000 ---p 00:00 0 -- 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/2fe00c4c-77a1-46b9-988a-c99724b9fb9cn%40googlegroups.com.
Re: Upgrading GWT-based application - issues with JEP-238 (MultiRelease) jar files
Thanks for responding! Meanwhile I am deploying to a local Tomcat (which is the target server anyway, so this also spares us issues caused by differences of the two...). On Thursday, July 29, 2021 at 12:51:20 PM UTC+2 Jens wrote: > But how can I replace the Jetty embedded in the GWT Maven plugin? Or is >> there some other way to work-around or fix this? >> > > You won't use the GWT Maven plugin to launch any GWT embedded Jetty. You > would use a Maven Jetty plugin directly to deploy your server side code. > Alternatively install Jetty on your host and tell it where to find *.war > files (or exploded war directories) generated by maven. > > > >> Would updating the GWT version to 2.8.2 or 2.9.0 solve this issue? >> > > No. Newest GWT uses embedded Jetty 9.2.x which does not support scanning > module-info.class files. > > > -- 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/0780db52-b505-42fc-a4c4-a443bc1928b2n%40googlegroups.com.
Upgrading GWT-based application - issues with JEP-238 (MultiRelease) jar files
I am trying to update the hibernate and spring versions used by a legacy
application which uses GWT 2.8.1. Doing so I ran into an issue when
starting the application using the GWT maven plugin's gwt:run or gwt:debug
commands - see the error message at the bottom.
Some search results that I found regarding that error suggest that the
embedded Jetty version has apparently issues with JEP-238 (MultiRelease)
jar files (i.e. .jar files that contain Java 9+ module info files). The
offending classmate-1.5.1.jar seems to be some transitive dependency of the
jackson JSON library and seems to contains such module info data.
Another reference stated that Jetty from v9.4.9 onwards supports such
multi-release .jar files.
But how can I replace the Jetty embedded in the GWT Maven plugin? Or is
there some other way to work-around or fix this?
Would updating the GWT version to 2.8.2 or 2.9.0 solve this issue?
Below is the error message that I get when starting up my application:
...
[WARN] Failed startup of context
c.g.g.d.s.j.WebAppContextWithReload@797f1e2a{/,file:/D:/Projects/RW-Tool/code/rwtool/web/target/rwtool-web-1.8.5-SNAPSHOT/,STARTING}{D:\Projects\RW-Tool\code\rwtool\web\target\rwtool-web-1.8.5-SNAPSHOT}
org.eclipse.jetty.util.MultiException: Multiple exceptions
at
org.eclipse.jetty.annotations.AnnotationConfiguration.scanForAnnotations(AnnotationConfiguration.java:536)
at
org.eclipse.jetty.annotations.AnnotationConfiguration.configure(AnnotationConfiguration.java:447)
at
org.eclipse.jetty.webapp.WebAppContext.configure(WebAppContext.java:479)
at
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1337)
at
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
at
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
at
com.google.gwt.dev.shell.jetty.JettyLauncher$WebAppContextWithReload.doStart(JettyLauncher.java:550)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
some lines removed for brevity ...
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at
com.google.gwt.dev.shell.jetty.JettyLauncher.start(JettyLauncher.java:760)
at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:636)
at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:923)
at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:706)
at com.google.gwt.dev.DevMode.main(DevMode.java:432)
Caused by: java.lang.RuntimeException: Error scanning entry
module-info.class from jar
file:/D:/Projects/RW-Tool/code/rwtool/web/target/rwtool-web-1.8.5-SNAPSHOT/WEB-INF/lib/classmate-1.5.1.jar
at
org.eclipse.jetty.annotations.AnnotationParser.parseJar(AnnotationParser.java:913)
at
org.eclipse.jetty.annotations.AnnotationParser.parse(AnnotationParser.java:831)
at
org.eclipse.jetty.annotations.AnnotationConfiguration$ParserTask.call(AnnotationConfiguration.java:163)
at
org.eclipse.jetty.annotations.AnnotationConfiguration$1.run(AnnotationConfiguration.java:548)
at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalArgumentException: null
at org.objectweb.asm.ClassReader.(Unknown Source)
at org.objectweb.asm.ClassReader.(Unknown Source)
at org.objectweb.asm.ClassReader.(Unknown Source)
at
org.eclipse.jetty.annotations.AnnotationParser.scanClass(AnnotationParser.java:973)
at
org.eclipse.jetty.annotations.AnnotationParser.parseJarEntry(AnnotationParser.java:956)
at
org.eclipse.jetty.annotations.AnnotationParser.parseJar(AnnotationParser.java:909)
at
org.eclipse.jetty.annotations.AnnotationParser.parse(AnnotationParser.java:831)
at
org.eclipse.jetty.annotations.AnnotationConfiguration$ParserTask.call(AnnotationConfiguration.java:163)
at
org.eclipse.jetty.annotations.AnnotationConfiguration$1.run(AnnotationConfiguration.java:548)
at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
at java.lang.Thread.run(Thread.java:748)
--
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/28b93a8d-971b-4ce0-97d3-88ed6e36n%40googlegroups.com.
