Re: A GWT components library - how to organize for Uibinder use?

Thanks Jens. This is my first Java project where I am sole architect. I ended up doing what you recommended, although I moved the ui.xml and css files into a sub-package to keep the top level package as clutter free as possible. 

On Saturday, November 30, 2024 at 5:49:08 PM UTC-6 Jens wrote:

UiBinder is XML and you have to import the package as namespace in order to use the components. Personally I would not create another package with classes extending the implementation because both classes would be public and both can be used in UiBinder then. That is likely confusing. I would put all components in the same package. Package private classes supporting a component could have the component name as prefix so they form a group in your IDE through sorting.

-- J.

cbruno...@gmail.com schrieb am Freitag, 29. November 2024 um 20:20:57 UTC+1:

Hello,

Im creating a component library for GWT and I want to be able to use the components in UI binder. However, when implementing my components, each component gets its own package, containing styles, and package private classes needed to build the component. 

However, to use in Uibinder, I need to do something like <m:button.Button text="Click" />

where m points to the package with my components.

Whats is bugging me is the extra "button" in the declaration. Is there anyway to flatten this aside from creating another package with objects simply extending the implementation ?

Thanks

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/6d1ef7bb-7da9-4027-9bb0-2a3d3d2c5d51n%40googlegroups.com.

Re: Servlet problem after upgrade

GWT doesn't really have any servlet magic so I doubt that the GWT upgrade has caused the issue. Are you double sure you haven't changed anything else except the GWT library? No Tomcat update? No Apache update? No update of Apache proxy rules? 

It sounds like your servlet is a GWT-RPC service because you used the Jakarta migration tool. If that is true you can now use gwt-servlet-jakarta.jar and skip the migration tool.

-- J.

dav...@googlemail.com schrieb am Samstag, 30. November 2024 um 17:27:59 UTC+1:

hi

I'm trying to upgrade from 2.10.0 to 2.12.1.

My app runs in tomcat / java 21 with apache using it as a proxy. It's mostly client code except for a servlet whose sole function is to grab the remote ip and make it available to client code. With the 2.10.0 setup I had to run the server class through the jakartaee migration tool to make it work. With everything ok, if you browse to the servlet you get a 405 as the GET method is not supported,  although that confirms the servlet is running.

With unchanged code everything compiles with 2.12.1,  but the servlet will not run. I've tried both the standard compiled class and its byte enhanced version. Both give a 404 and the ip is not available to client code. The client code itself otherwise runs as expected.

Any pointers towards a fix?

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/dda2b7e2-3565-4f79-ac99-b90f8cac9522n%40googlegroups.com.

Re: A GWT components library - how to organize for Uibinder use?

UiBinder is XML and you have to import the package as namespace in order to use the components. Personally I would not create another package with classes extending the implementation because both classes would be public and both can be used in UiBinder then. That is likely confusing. I would put all components in the same package. Package private classes supporting a component could have the component name as prefix so they form a group in your IDE through sorting.

-- J.

cbruno...@gmail.com schrieb am Freitag, 29. November 2024 um 20:20:57 UTC+1:

Hello,

Im creating a component library for GWT and I want to be able to use the components in UI binder. However, when implementing my components, each component gets its own package, containing styles, and package private classes needed to build the component. 

However, to use in Uibinder, I need to do something like <m:button.Button text="Click" />

where m points to the package with my components.

Whats is bugging me is the extra "button" in the declaration. Is there anyway to flatten this aside from creating another package with objects simply extending the implementation ?

Thanks

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/5186c8d1-ab87-4741-b4f9-54f4d579dd24n%40googlegroups.com.

Servlet problem after upgrade

hi

I'm trying to upgrade from 2.10.0 to 2.12.1.

My app runs in tomcat / java 21 with apache using it as a proxy. It's mostly client code except for a servlet whose sole function is to grab the remote ip and make it available to client code. With the 2.10.0 setup I had to run the server class through the jakartaee migration tool to make it work. With everything ok, if you browse to the servlet you get a 405 as the GET method is not supported,  although that confirms the servlet is running.

With unchanged code everything compiles with 2.12.1,  but the servlet will not run. I've tried both the standard compiled class and its byte enhanced version. Both give a 404 and the ip is not available to client code. The client code itself otherwise runs as expected.

Any pointers towards a fix?

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/cffd13f6-80f3-44fd-9351-5db19d16ce58n%40googlegroups.com.

A GWT components library - how to organize for Uibinder use?

Hello,

Im creating a component library for GWT and I want to be able to use the components in UI binder. However, when implementing my components, each component gets its own package, containing styles, and package private classes needed to build the component. 

However, to use in Uibinder, I need to do something like <m:button.Button text="Click" />

where m points to the package with my components.

Whats is bugging me is the extra "button" in the declaration. Is there anyway to flatten this aside from creating another package with objects simply extending the implementation ?

Thanks

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/5b19f21c-ab5c-4d51-8396-99869b844fc4n%40googlegroups.com.

Re: Firefox - mouse wheel

On Friday, November 29, 2024 at 8:36:48 AM UTC+1 had...@digitech.cz wrote:

Thanks, 

I am using gwt-openlayers-client 1.1.0, not TDesjardins/gwt-ol.

The one released nearly 8 years ago‽

It apparently doesn't use mousewheel event itself either, like GWT-OL (and I see you opened an issue there)

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/307120d6-87b8-4c28-9fc1-2e68f88d9197n%40googlegroups.com.

Re: Firefox - mouse wheel

Thanks, 

I am using gwt-openlayers-client 1.1.0, not TDesjardins/gwt-ol.

čt 28. 11. 2024 v 12:53 odesílatel Thomas Broyer <t.broyer@gmail.com> napsal:

Most likely culprit from the release notes:

• The mousewheel event has been deprecated in browsers, its usage in GWT has been replaced with the wheel event. This should be transparent to applications.

That being said, GWT-OL doesn't itself handles those events so possibly unrelated actually.

Wrt permutations, this is due to removal of support for IE 8, 9 and 10 in 2.10.0, leaving only "safari" (for all WebKit or Chromium based browsers) and "gecko1_8" (for Firefox and IE 11)

On Thursday, November 28, 2024 at 12:25:15 PM UTC+1 had...@digitech.cz wrote:

I upgraded GWT from 2.8 to 2.12, and in Firefox mouse wheel scroll stopped  working in some components (notably GwtOpenLayers component). 

I noted that previously my project had 5 permutations, now it is 2 permutations:

Compiling 2 permutations

     Compiling permutation 0...

      Compiling permutation 1...

So, perhaps these iterations are related to various browser engine support, and I have Firefox support disabled (wild guess)? Somebody with similar problem in Firefox?

Mirza

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/1ddc9b3b-348c-43fb-992f-8eb1f677cee5n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/CAOvMoHXqz_p6MxPYaFjG1uy%3Dq_Ms-yNLT%3DtvbYN17jBJK%2BqxOw%40mail.gmail.com.

Re: Firefox - mouse wheel

Most likely culprit from the release notes:

• The mousewheel event has been deprecated in browsers, its usage in GWT has been replaced with the wheel event. This should be transparent to applications.

That being said, GWT-OL doesn't itself handles those events so possibly unrelated actually.

Wrt permutations, this is due to removal of support for IE 8, 9 and 10 in 2.10.0, leaving only "safari" (for all WebKit or Chromium based browsers) and "gecko1_8" (for Firefox and IE 11)

On Thursday, November 28, 2024 at 12:25:15 PM UTC+1 had...@digitech.cz wrote:

I upgraded GWT from 2.8 to 2.12, and in Firefox mouse wheel scroll stopped  working in some components (notably GwtOpenLayers component). 

I noted that previously my project had 5 permutations, now it is 2 permutations:

Compiling 2 permutations

     Compiling permutation 0...

      Compiling permutation 1...

So, perhaps these iterations are related to various browser engine support, and I have Firefox support disabled (wild guess)? Somebody with similar problem in Firefox?

Mirza

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/1ddc9b3b-348c-43fb-992f-8eb1f677cee5n%40googlegroups.com.

Firefox - mouse scroll

Hello,

I upgraded GWT from 2.8 to 2.12, and in Firefox mouse wheel scroll stopped  working in some components (notably GwtOpenLayers component). 

I noted that previously my project had 5 permutations, now it is 2 permutations:

Compiling 2 permutations

     Compiling permutation 0...

      Compiling permutation 1...

So, perhaps these iterations are related to various browser engine support, and I have Firefox support disabled (wild guess)? Somebody with similar problem in Firefox?

Mirza

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/CAOvMoHXb-uUUYGH8FmdaOKem%2Bj1i%3Dbx4vbUZc_qCSaWTXhPtEA%40mail.gmail.com.

Re: Issue with enhanced switch statements in GWT 2.12.1

Thanks, this was filed at https://github.com/gwtproject/gwt/issues/10044. The issue is that we misunderstood how the JDT AST handled this case (assumed it was a block ending in a break, rather than a yield with a void expression, which isn't legal in Java), and the tests didn't check for flow in the method after the switch was finished (it is a little awkward to put an assert after a code block and validate not just that it passes but was run at all. We'll get this fixed soon, with better tests as well.

On Thursday, November 21, 2024 at 4:17:32 AM UTC-6 vas...@gmail.com wrote:

lack of caffeine indeed.

Somehow the sentence that was explaining the problem disappeared for me between scrolls..

Sorry

On Thu, Nov 21, 2024 at 10:38 AM Vassilis Virvilis <vas...@gmail.com> wrote:

I must be low on caffeine because I can't see the problem.

Is the problem that it doesn't print:

Test 2 - Done

at the end?

On Thu, Nov 21, 2024 at 10:28 AM Craig Mitchell <ma...@craig-mitchell.com> wrote:

The release notes for 2.12.1 ( https://www.gwtproject.org/release-notes.html#Release_Notes_2_12_1 ) say:

> Switch statements can correctly compile without being contained in braces

For me, they compile, but they don't work.  Eg.  This code:

GWT.log("Test 1 - Start");
switch (1) {
  case 1 -> {
    GWT.log("Test 1 - 1");
  }
  case 2 -> {
    GWT.log("Test 1 - 2");
  }
  case 3 -> {
    GWT.log("Test 1 - 3");
  }
}
GWT.log("Test 1 - Done");

GWT.log("Test 2 - Start");
switch (1) {
  case 1 -> GWT.log("Test 2 - 1");
  case 2 -> GWT.log("Test 2 - 2");
  case 3 -> GWT.log("Test 2 - 3");
}
GWT.log("Test 2 - Done");

Will never get to the last "Test 2 - Done" line.  The output will be:

Test 1 - Start
Test 1 - 1
Test 1 - Done
Test 2 - Start
Test 2 - 1

Is this a known issue?

Thanks.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-tool...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/d0b4fe79-0571-481a-bf4f-c8ccda40e486n%40googlegroups.com.

--

Vassilis Virvilis

--

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+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/51661537-7faf-4e9f-a6e5-41e331f17e8fn%40googlegroups.com.

Re: Issue with enhanced switch statements in GWT 2.12.1

lack of caffeine indeed.

Somehow the sentence that was explaining the problem disappeared for me between scrolls..

Sorry

On Thu, Nov 21, 2024 at 10:38 AM Vassilis Virvilis <vasvir2@gmail.com> wrote:

I must be low on caffeine because I can't see the problem.

Is the problem that it doesn't print:

Test 2 - Done

at the end?

On Thu, Nov 21, 2024 at 10:28 AM Craig Mitchell <mail@craig-mitchell.com> wrote:

The release notes for 2.12.1 ( https://www.gwtproject.org/release-notes.html#Release_Notes_2_12_1 ) say:

> Switch statements can correctly compile without being contained in braces

For me, they compile, but they don't work.  Eg.  This code:

GWT.log("Test 1 - Start");
switch (1) {
  case 1 -> {
    GWT.log("Test 1 - 1");
  }
  case 2 -> {
    GWT.log("Test 1 - 2");
  }
  case 3 -> {
    GWT.log("Test 1 - 3");
  }
}
GWT.log("Test 1 - Done");

GWT.log("Test 2 - Start");
switch (1) {
  case 1 -> GWT.log("Test 2 - 1");
  case 2 -> GWT.log("Test 2 - 2");
  case 3 -> GWT.log("Test 2 - 3");
}
GWT.log("Test 2 - Done");

Will never get to the last "Test 2 - Done" line.  The output will be:

Test 1 - Start
Test 1 - 1
Test 1 - Done
Test 2 - Start
Test 2 - 1

Is this a known issue?

Thanks.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/d0b4fe79-0571-481a-bf4f-c8ccda40e486n%40googlegroups.com.

--

Vassilis Virvilis

--

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+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/CAKbOjEwsxyVcvfy_7nvPfn%3DYb%2BQr9pDBU6xcOYtOcu1gvk1xFg%40mail.gmail.com.

Re: Issue with enhanced switch statements in GWT 2.12.1

Thanks Thomas.  Yes, that's the same issue.  I've now commented on it.  Cheers.

On Thursday, 21 November 2024 at 8:04:39 pm UTC+11 Thomas Broyer wrote:

Could be related to https://github.com/gwtproject/gwt/issues/10044

Fwiw, the issue fixed in 2.12.1 was not about the "case x -> foo" vs "case x -> { foo }" but about enclosing the whole switch inside a block.

On Thursday, November 21, 2024 at 9:28:51 AM UTC+1 ma...@craig-mitchell.com wrote:

The release notes for 2.12.1 ( https://www.gwtproject.org/release-notes.html#Release_Notes_2_12_1 ) say:

> Switch statements can correctly compile without being contained in braces

For me, they compile, but they don't work.  Eg.  This code:

GWT.log("Test 1 - Start");
switch (1) {
  case 1 -> {
    GWT.log("Test 1 - 1");
  }
  case 2 -> {
    GWT.log("Test 1 - 2");
  }
  case 3 -> {
    GWT.log("Test 1 - 3");
  }
}
GWT.log("Test 1 - Done");

GWT.log("Test 2 - Start");
switch (1) {
  case 1 -> GWT.log("Test 2 - 1");
  case 2 -> GWT.log("Test 2 - 2");
  case 3 -> GWT.log("Test 2 - 3");
}
GWT.log("Test 2 - Done");

Will never get to the last "Test 2 - Done" line.  The output will be:

Test 1 - Start
Test 1 - 1
Test 1 - Done
Test 2 - Start
Test 2 - 1

Is this a known issue?

Thanks.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/813a36c4-81cc-44af-97ab-48cfdb04289fn%40googlegroups.com.

Re: Issue with enhanced switch statements in GWT 2.12.1

Could be related to https://github.com/gwtproject/gwt/issues/10044

Fwiw, the issue fixed in 2.12.1 was not about the "case x -> foo" vs "case x -> { foo }" but about enclosing the whole switch inside a block.

On Thursday, November 21, 2024 at 9:28:51 AM UTC+1 ma...@craig-mitchell.com wrote:

The release notes for 2.12.1 ( https://www.gwtproject.org/release-notes.html#Release_Notes_2_12_1 ) say:

> Switch statements can correctly compile without being contained in braces

For me, they compile, but they don't work.  Eg.  This code:

GWT.log("Test 1 - Start");
switch (1) {
  case 1 -> {
    GWT.log("Test 1 - 1");
  }
  case 2 -> {
    GWT.log("Test 1 - 2");
  }
  case 3 -> {
    GWT.log("Test 1 - 3");
  }
}
GWT.log("Test 1 - Done");

GWT.log("Test 2 - Start");
switch (1) {
  case 1 -> GWT.log("Test 2 - 1");
  case 2 -> GWT.log("Test 2 - 2");
  case 3 -> GWT.log("Test 2 - 3");
}
GWT.log("Test 2 - Done");

Will never get to the last "Test 2 - Done" line.  The output will be:

Test 1 - Start
Test 1 - 1
Test 1 - Done
Test 2 - Start
Test 2 - 1

Is this a known issue?

Thanks.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/2ce64938-712b-4d56-902a-5a922a5d158dn%40googlegroups.com.

Re: Issue with enhanced switch statements in GWT 2.12.1

I must be low on caffeine because I can't see the problem.

Is the problem that it doesn't print:

Test 2 - Done

at the end?

On Thu, Nov 21, 2024 at 10:28 AM Craig Mitchell <mail@craig-mitchell.com> wrote:

The release notes for 2.12.1 ( https://www.gwtproject.org/release-notes.html#Release_Notes_2_12_1 ) say:

> Switch statements can correctly compile without being contained in braces

For me, they compile, but they don't work.  Eg.  This code:

GWT.log("Test 1 - Start");
switch (1) {
  case 1 -> {
    GWT.log("Test 1 - 1");
  }
  case 2 -> {
    GWT.log("Test 1 - 2");
  }
  case 3 -> {
    GWT.log("Test 1 - 3");
  }
}
GWT.log("Test 1 - Done");

GWT.log("Test 2 - Start");
switch (1) {
  case 1 -> GWT.log("Test 2 - 1");
  case 2 -> GWT.log("Test 2 - 2");
  case 3 -> GWT.log("Test 2 - 3");
}
GWT.log("Test 2 - Done");

Will never get to the last "Test 2 - Done" line.  The output will be:

Test 1 - Start
Test 1 - 1
Test 1 - Done
Test 2 - Start
Test 2 - 1

Is this a known issue?

Thanks.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/d0b4fe79-0571-481a-bf4f-c8ccda40e486n%40googlegroups.com.

--

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+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/CAKbOjEytjRYrFc4FDmgwagH_CpWCPkW6eWf2F_pW_ywqmAXb-g%40mail.gmail.com.

Issue with enhanced switch statements in GWT 2.12.1

The release notes for 2.12.1 ( https://www.gwtproject.org/release-notes.html#Release_Notes_2_12_1 ) say:

> Switch statements can correctly compile without being contained in braces

For me, they compile, but they don't work.  Eg.  This code:

GWT.log("Test 1 - Start");
switch (1) {
  case 1 -> {
    GWT.log("Test 1 - 1");
  }
  case 2 -> {
    GWT.log("Test 1 - 2");
  }
  case 3 -> {
    GWT.log("Test 1 - 3");
  }
}
GWT.log("Test 1 - Done");

GWT.log("Test 2 - Start");
switch (1) {
  case 1 -> GWT.log("Test 2 - 1");
  case 2 -> GWT.log("Test 2 - 2");
  case 3 -> GWT.log("Test 2 - 3");
}
GWT.log("Test 2 - Done");

Will never get to the last "Test 2 - Done" line.  The output will be:

Test 1 - Start
Test 1 - 1
Test 1 - Done
Test 2 - Start
Test 2 - 1

Is this a known issue?

Thanks.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/d0b4fe79-0571-481a-bf4f-c8ccda40e486n%40googlegroups.com.

Re: GWT 2.12.0 with net.ltgt.gwt.maven gwt maven plugin: [ERROR] Unable to find 'com/medhok/mm/OEV.gwt.xml' on your classpath; could be a typo, or maybe you forgot to include a classpath entry for source?

Thanks Colin,  Removing the -compileReport argument solved the problem.  Now I will proceed with my java 21 upgrade changes.

Thank you so much for your inputs.

On Monday, November 18, 2024 at 4:02:00 PM UTC-5 Venkateswara Rao wrote:

Thanks for your response Colin,  gwt.user.agent we defined to pass few. However, let me remove compileReport and run the debug level and share it with you.

On Monday, November 18, 2024 at 11:23:25 AM UTC-5 Colin Alworth wrote:

Adding more workers will not necessarily make it faster - if you are near your memory limit, it may be slower because the system could spend more time GCing so that the threads can each get their own work done. Even if you are not near the memory limit, it may make it slower, depending on how fast your CPU/memory is in moving data back and forth. Can you share the full successful build log, both before and after?

There is no system property "gwt.user.agent" in GWT itself (maybe this is specific to smartgwt?). Perhaps you mean to be passing -setProperty user.agent=.. instead as an arg to GWT? That would remove your other permutations.

Thomas's suggestion is to get _all_ of the arguments, not just the ones you're setting by hand. Likewise, try to take the measurements I suggested. Can you also share the full build log - GWT doesn't log the word "Done" at INFO level except when you have detailed SOYC enabled (-XdetailedSoyc), which is documented to consume extra compile time to write so much output. I note that you do have "-compileReport" turned on - are you sure you want that at all?

On Monday, November 18, 2024 at 10:11:24 AM UTC-6 venkat...@gmail.com wrote:

Thanks Colin for your response.  To answer your question,

My current project is using Java 8, GWT 2.11.0, smartgwt 12.0P with mojo codehaus plugin 2.10.0, when I build with following arguments:

<extraJvmArgs>-Xmx7G -XX:+UseG1GC -Dgwt.user.agent=${gwt.compile.user.agent}</extraJvmArgs>

It will take approximately 8 mins to finish the build process.

Now we are upgrading to new plugin net.ltgt.gwt.maven and provided with same arguments.  This one is taking too much time more than 4 hours eventhough I added localWorkers 4.

Appreciate your inputs on this.

Thanks.

On Monday, November 18, 2024 at 10:57:11 AM UTC-5 Colin Alworth wrote:

Is it taking longer than it used to, or hanging and staying stuck? How long did it used to take, how long does it take now (if not actually stuck)?

Have you tried giving it more than 7GB of memory, or using the default GC instead of g1? G1 is the default for Java 17+, and can handle a lot of memory (depending on your project size it may need quite a bit), and is fairly configurable. How much memory did this stage actually use (not just allocated, but used) before you changed the GWT plugin?

Have you attempted any profiling of the process? Is there any chance that your disk is full...?

To confirm, you are _not_ updating GWT, just the plugin first, right?

If you can share the sample project you created, please put it on github or the like and link from this - one of us can try to build it and see what is broken with your project.

If you'd like to share code privately and have a videocall to wrap this up, that is a service that our company offers, you can contact me off-list at co...@vertispan.com.

On Monday, November 18, 2024 at 9:42:36 AM UTC-6 venkat...@gmail.com wrote:

Please help me on this issue, It's taking too much time to build GWT application.

Any inputs would help me to proceed further.

Thanks.

On Friday, November 15, 2024 at 4:41:06 PM UTC-5 Venkateswara Rao wrote:

Any update on this issue, I have enabled debug logs and added localworkers 4. Issue still persists..

[INFO]          Done
 

It's says Done in the log.

Thanks.

On Thursday, November 14, 2024 at 9:17:32 PM UTC-5 Venkateswara Rao wrote:

Thomas Broyer,

Thanks for your response.  I have added the jvmArgs and systemProperties to the plugin as mentioned below:

<plugin>

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

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

<version>1.1.0</version>

<executions>

<execution>

<goals>

<goal>compile</goal>

</goals>

</execution>

</executions>

<configuration>

<moduleName>com.medhok.mm.OEV</moduleName>

<failOnError>true</failOnError>

<!-- GWT compiler 2.8 and above requires 1.8, hence define sourceLevel here if you use

a different source language for java compilation -->

<sourceLevel>1.8</sourceLevel>

<!-- Compiler configuration -->

<compilerArgs>

<!-- Ask GWT to create the Story of Your Compile (SOYC) (gwt:compile) -->

<arg>-compileReport</arg>

<!--<arg>-XcompilerMetrics</arg>-->

</compilerArgs>

<jvmArgs>

<arg>-Xmx7G</arg>

<arg>-XX:+UseG1GC</arg>

</jvmArgs>

<systemProperties>

<gwt.user.agent>${gwt.compile.user.agent}</gwt.user.agent>

</systemProperties>

<!-- DevMode configuration -->

<warDir>${project.build.directory}/${project.build.finalName}</warDir>

<classpathScope>compile+runtime</classpathScope>

<!-- URL(s) that should be opened by DevMode (gwt:devmode). -->

<startupUrls>

<startupUrl>index.html</startupUrl>

</startupUrls>

</configuration>

</plugin>

Now, It's hanged on Compiling Permutations 0..

Please let me know what's the wrong in the configuration.

On Thursday, November 14, 2024 at 7:04:07 PM UTC-5 Thomas Broyer wrote:

On Thursday, November 14, 2024 at 4:34:40 PM UTC+1 venkat...@gmail.com wrote:

@Thomas Broyer,

What will be the equivalent argument for the following in the new plugin:

<extraJvmArgs>-Xmx7G -XX:+UseG1GC -Dgwt.user.agent=${gwt.compile.user.agent}</extraJvmArgs>

Thanks.

<jvmArgs> and <systemProperties> https://tbroyer.github.io/gwt-maven-plugin/compile-mojo.html

<jvmArgs>

  <arg>-Xmx7G</arg>

  <arg>-XX:+UseG1GC</arg>

</jvmArgs>

<systemProperties>

  <gwt.user.agent>${gwt.compile.user.agent}</gwt.user.agent>

</systemProperties>

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/048e79ed-1226-4bf5-b231-ca2d36cf19ecn%40googlegroups.com.

Re: GWT 2.12.0 with net.ltgt.gwt.maven gwt maven plugin: [ERROR] Unable to find 'com/medhok/mm/OEV.gwt.xml' on your classpath; could be a typo, or maybe you forgot to include a classpath entry for source?

Thanks for your response Colin,  gwt.user.agent we defined to pass few. However, let me remove compileReport and run the debug level and share it with you.

On Monday, November 18, 2024 at 11:23:25 AM UTC-5 Colin Alworth wrote:

Adding more workers will not necessarily make it faster - if you are near your memory limit, it may be slower because the system could spend more time GCing so that the threads can each get their own work done. Even if you are not near the memory limit, it may make it slower, depending on how fast your CPU/memory is in moving data back and forth. Can you share the full successful build log, both before and after?

There is no system property "gwt.user.agent" in GWT itself (maybe this is specific to smartgwt?). Perhaps you mean to be passing -setProperty user.agent=.. instead as an arg to GWT? That would remove your other permutations.

Thomas's suggestion is to get _all_ of the arguments, not just the ones you're setting by hand. Likewise, try to take the measurements I suggested. Can you also share the full build log - GWT doesn't log the word "Done" at INFO level except when you have detailed SOYC enabled (-XdetailedSoyc), which is documented to consume extra compile time to write so much output. I note that you do have "-compileReport" turned on - are you sure you want that at all?

On Monday, November 18, 2024 at 10:11:24 AM UTC-6 venkat...@gmail.com wrote:

Thanks Colin for your response.  To answer your question,

My current project is using Java 8, GWT 2.11.0, smartgwt 12.0P with mojo codehaus plugin 2.10.0, when I build with following arguments:

<extraJvmArgs>-Xmx7G -XX:+UseG1GC -Dgwt.user.agent=${gwt.compile.user.agent}</extraJvmArgs>

It will take approximately 8 mins to finish the build process.

Now we are upgrading to new plugin net.ltgt.gwt.maven and provided with same arguments.  This one is taking too much time more than 4 hours eventhough I added localWorkers 4.

Appreciate your inputs on this.

Thanks.

On Monday, November 18, 2024 at 10:57:11 AM UTC-5 Colin Alworth wrote:

Is it taking longer than it used to, or hanging and staying stuck? How long did it used to take, how long does it take now (if not actually stuck)?

Have you tried giving it more than 7GB of memory, or using the default GC instead of g1? G1 is the default for Java 17+, and can handle a lot of memory (depending on your project size it may need quite a bit), and is fairly configurable. How much memory did this stage actually use (not just allocated, but used) before you changed the GWT plugin?

Have you attempted any profiling of the process? Is there any chance that your disk is full...?

To confirm, you are _not_ updating GWT, just the plugin first, right?

If you can share the sample project you created, please put it on github or the like and link from this - one of us can try to build it and see what is broken with your project.

If you'd like to share code privately and have a videocall to wrap this up, that is a service that our company offers, you can contact me off-list at co...@vertispan.com.

On Monday, November 18, 2024 at 9:42:36 AM UTC-6 venkat...@gmail.com wrote:

Please help me on this issue, It's taking too much time to build GWT application.

Any inputs would help me to proceed further.

Thanks.

On Friday, November 15, 2024 at 4:41:06 PM UTC-5 Venkateswara Rao wrote:

Any update on this issue, I have enabled debug logs and added localworkers 4. Issue still persists..

[INFO]          Done
 

It's says Done in the log.

Thanks.

On Thursday, November 14, 2024 at 9:17:32 PM UTC-5 Venkateswara Rao wrote:

Thomas Broyer,

Thanks for your response.  I have added the jvmArgs and systemProperties to the plugin as mentioned below:

<plugin>

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

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

<version>1.1.0</version>

<executions>

<execution>

<goals>

<goal>compile</goal>

</goals>

</execution>

</executions>

<configuration>

<moduleName>com.medhok.mm.OEV</moduleName>

<failOnError>true</failOnError>

<!-- GWT compiler 2.8 and above requires 1.8, hence define sourceLevel here if you use

a different source language for java compilation -->

<sourceLevel>1.8</sourceLevel>

<!-- Compiler configuration -->

<compilerArgs>

<!-- Ask GWT to create the Story of Your Compile (SOYC) (gwt:compile) -->

<arg>-compileReport</arg>

<!--<arg>-XcompilerMetrics</arg>-->

</compilerArgs>

<jvmArgs>

<arg>-Xmx7G</arg>

<arg>-XX:+UseG1GC</arg>

</jvmArgs>

<systemProperties>

<gwt.user.agent>${gwt.compile.user.agent}</gwt.user.agent>

</systemProperties>

<!-- DevMode configuration -->

<warDir>${project.build.directory}/${project.build.finalName}</warDir>

<classpathScope>compile+runtime</classpathScope>

<!-- URL(s) that should be opened by DevMode (gwt:devmode). -->

<startupUrls>

<startupUrl>index.html</startupUrl>

</startupUrls>

</configuration>

</plugin>

Now, It's hanged on Compiling Permutations 0..

Please let me know what's the wrong in the configuration.

On Thursday, November 14, 2024 at 7:04:07 PM UTC-5 Thomas Broyer wrote:

On Thursday, November 14, 2024 at 4:34:40 PM UTC+1 venkat...@gmail.com wrote:

@Thomas Broyer,

What will be the equivalent argument for the following in the new plugin:

<extraJvmArgs>-Xmx7G -XX:+UseG1GC -Dgwt.user.agent=${gwt.compile.user.agent}</extraJvmArgs>

Thanks.

<jvmArgs> and <systemProperties> https://tbroyer.github.io/gwt-maven-plugin/compile-mojo.html

<jvmArgs>

  <arg>-Xmx7G</arg>

  <arg>-XX:+UseG1GC</arg>

</jvmArgs>

<systemProperties>

  <gwt.user.agent>${gwt.compile.user.agent}</gwt.user.agent>

</systemProperties>

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/e5c46a82-ebef-44fc-b9d5-5ffeaa64639an%40googlegroups.com.

GWT Project,COLLECTIVE,Open source,java,javascript

Would it be a good idea to have a donate link added to the footer of mailing list emails?

On 11/15/24 20:37, Colin Alworth wrote:

We have an      - we mention it on release announcements, but don't emphasize it much beyond that.

On Friday, November 15, 2024 at 4:51:23 PM UTC-6 B...@lacatena.net wrote:

That did it, and switching to 2.12.1 solved the other problem I was having (out of memory error looking like it was due to some sort of recursive calls in GWT compilation triggered by I don't know what).  I just got lucky that I was coming here to ask for help on that, saw 2.12.1, and thought, "gee, I wonder if it's a bug they already fixed..."

Thanks again for your help.  Does the GWT Project have a Donate button somewhere?

On Friday, November 15, 2024 at 4:48:13 PM UTC-5 Bob Lacatena wrote:

I think that's it... I found a stray.  Also, it built and ran fine on the server.  The stray is in the dependencies in the GWT run config, automatically added because it was lying around in web/WEB-INF/lib.  Thanks for the clues.

On Friday, November 15, 2024 at 4:37:46 PM UTC-5 Colin Alworth wrote:

You have a mixed classpath of old and new GWT somehow. Verify both that gwt-user and gwt-dev match their version, and that you aren't mixing org.gwtproject and com.google.gwt groupIds (use the gwt BOM/platform dependencies to ensure this is resolved).

On Friday, November 15, 2024 at 3:33:26 PM UTC-6 B...@lacatena.net wrote:

Sorry, I realized the caused by part of it was more important.  Here's the whole thing.

I just ran a gradle build (after first manually deleting all cached stuff so it would be clean), and that said it completed fine... the error happens when I visit the page.  I am going to try now to run the build on the server and test the deployed app.  I'll get back to you on that.

I meant to ask before.. should I file this as an issue in GitHub?  I assume that's how you work, but thought I'd confirm first.

GET /recompile/com.insightxp.i2g.I2g

Job com.insightxp.i2g.I2g_1_0

starting job: com.insightxp.i2g.I2g_1_0

binding: locale=en

binding: user.agent=safari

Compiling module com.insightxp.i2g.I2g

[ERROR] An internal compiler exception occurred

com.google.gwt.dev.jjs.InternalCompilerException: Unexpected error during visit.

at com.google.gwt.dev.jjs.ast.JVisitor.translateException(JVisitor.java:111)

at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:276)

at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:265)

at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:118)

at com.google.gwt.dev.jjs.ast.JCastOperation.traverse(JCastOperation.java:76)

at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361)

at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273)

at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:265)

at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:118)

at com.google.gwt.dev.jjs.ast.JBinaryOperation.traverse(JBinaryOperation.java:89)

at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361)

at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273)

at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:265)

at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:118)

at com.google.gwt.dev.jjs.ast.JExpressionStatement.traverse(JExpressionStatement.java:42)

at com.google.gwt.dev.jjs.ast.JModVisitor$ListContext.traverse(JModVisitor.java:88)

at com.google.gwt.dev.jjs.ast.JModVisitor.acceptWithInsertRemove(JModVisitor.java:331)

at com.google.gwt.dev.jjs.ast.JBlock.traverse(JBlock.java:94)

at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361)

at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273)

at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:139)

at com.google.gwt.dev.jjs.ast.JIfStatement.traverse(JIfStatement.java:53)

at com.google.gwt.dev.jjs.ast.JModVisitor$ListContext.traverse(JModVisitor.java:88)

at com.google.gwt.dev.jjs.ast.JModVisitor.acceptWithInsertRemove(JModVisitor.java:331)

at com.google.gwt.dev.jjs.ast.JBlock.traverse(JBlock.java:94)

at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361)

at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273)

at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:139)

at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:135)

at com.google.gwt.dev.jjs.ast.JMethodBody.traverse(JMethodBody.java:83)

at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361)

at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273)

at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:265)

at com.google.gwt.dev.jjs.ast.JMethod.visitChildren(JMethod.java:786)

at com.google.gwt.dev.jjs.ast.JMethod.traverse(JMethod.java:778)

at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361)

at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273)

at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:265)

at com.google.gwt.dev.jjs.impl.UnifyAst.mainLoop(UnifyAst.java:1407)

at com.google.gwt.dev.jjs.impl.UnifyAst.exec(UnifyAst.java:902)

at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.unifyJavaAst(JavaToJavaScriptCompiler.java:1404)

at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.constructJavaAst(JavaToJavaScriptCompiler.java:1216)

at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.precompile(JavaToJavaScriptCompiler.java:1131)

at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.precompile(JavaToJavaScriptCompiler.java:257)

at com.google.gwt.dev.Precompile.precompile(Precompile.java:243)

at com.google.gwt.dev.Precompile.precompile(Precompile.java:190)

at com.google.gwt.dev.Precompile.precompile(Precompile.java:131)

at com.google.gwt.dev.Compiler.compile(Compiler.java:192)

at com.google.gwt.dev.codeserver.Recompiler.doCompile(Recompiler.java:362)

at com.google.gwt.dev.codeserver.Recompiler.compile(Recompiler.java:175)

at com.google.gwt.dev.codeserver.Recompiler.recompile(Recompiler.java:134)

at com.google.gwt.dev.codeserver.Outbox.recompile(Outbox.java:135)

at com.google.gwt.dev.codeserver.JobRunner.recompile(JobRunner.java:113)

at com.google.gwt.dev.codeserver.JobRunner.access$000(JobRunner.java:37)

at com.google.gwt.dev.codeserver.JobRunner$2.run(JobRunner.java:90)

at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)

at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)

at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)

at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)

at java.base/java.lang.Thread.run(Thread.java:842)

Caused by: java.lang.NoSuchMethodError: 'void com.google.gwt.thirdparty.guava.common.base.Preconditions.checkState(boolean, java.lang.String, java.lang.Object)'

at com.google.gwt.safehtml.rebind.HtmlTemplateParser.getHtmlContextFromParseState(HtmlTemplateParser.java:269)

at com.google.gwt.safehtml.rebind.HtmlTemplateParser.parseTemplate(HtmlTemplateParser.java:205)

at com.google.gwt.safehtml.rebind.SafeHtmlTemplatesImplMethodCreator.emitMethodBodyFromTemplate(SafeHtmlTemplatesImplMethodCreator.java:220)

at com.google.gwt.safehtml.rebind.SafeHtmlTemplatesImplMethodCreator.createMethodFor(SafeHtmlTemplatesImplMethodCreator.java:120)

at com.google.gwt.safehtml.rebind.SafeHtmlTemplatesImplCreator.emitMethodBody(SafeHtmlTemplatesImplCreator.java:43)

at com.google.gwt.user.rebind.AbstractGeneratorClassCreator.genMethod(AbstractGeneratorClassCreator.java:277)

at com.google.gwt.user.rebind.AbstractGeneratorClassCreator.emitMethods(AbstractGeneratorClassCreator.java:239)

at com.google.gwt.user.rebind.AbstractGeneratorClassCreator.emitClass(AbstractGeneratorClassCreator.java:118)

at com.google.gwt.safehtml.rebind.SafeHtmlTemplatesGenerator.generate(SafeHtmlTemplatesGenerator.java:65)

at com.google.gwt.core.ext.IncrementalGenerator.generateNonIncrementally(IncrementalGenerator.java:40)

at com.google.gwt.dev.javac.StandardGeneratorContext.runGeneratorIncrementally(StandardGeneratorContext.java:745)

at com.google.gwt.dev.cfg.RuleGenerateWith.realize(RuleGenerateWith.java:103)

at com.google.gwt.dev.shell.StandardRebindOracle$Rebinder.rebind(StandardRebindOracle.java:78)

at com.google.gwt.dev.shell.StandardRebindOracle.rebind(StandardRebindOracle.java:262)

at com.google.gwt.dev.shell.StandardRebindOracle.rebind(StandardRebindOracle.java:251)

at com.google.gwt.dev.PrecompilationContextCreator$1.getAllPossibleRebindAnswers(PrecompilationContextCreator.java:86)

at com.google.gwt.dev.jjs.impl.UnifyAst$UnifyVisitor.createStaticRebindExpression(UnifyAst.java:525)

at com.google.gwt.dev.jjs.impl.UnifyAst$UnifyVisitor.createRebindExpression(UnifyAst.java:493)

at com.google.gwt.dev.jjs.impl.UnifyAst$UnifyVisitor.maybeHandleMagicMethodCall(UnifyAst.java:421)

at com.google.gwt.dev.jjs.impl.UnifyAst$UnifyVisitor.visit(UnifyAst.java:408)

at com.google.gwt.dev.jjs.ast.JMethodCall.traverse(JMethodCall.java:265)

at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361)

at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273)

... 58 more

[ERROR] at ClippedImageImpl.java(106): GWT.create(ClippedImageImpl$DraggableTemplate.class)

com.google.gwt.dev.jjs.ast.JMethodCall

[ERROR] at ClippedImageImpl.java(106): (ClippedImageImpl$DraggableTemplate) GWT.create(ClippedImageImpl$DraggableTemplate.class)

com.google.gwt.dev.jjs.ast.JCastOperation

[ERROR] at ClippedImageImpl.java(106): ClippedImageImpl.draggableTemplate = (ClippedImageImpl$DraggableTemplate) GWT.create(ClippedImageImpl$DraggableTemplate.class)

com.google.gwt.dev.jjs.ast.JBinaryOperation

[ERROR] at ClippedImageImpl.java(106): ClippedImageImpl.draggableTemplate = (ClippedImageImpl$DraggableTemplate) GWT.create(ClippedImageImpl$DraggableTemplate.class)

com.google.gwt.dev.jjs.ast.JExpressionStatement

[ERROR] at ClippedImageImpl.java(105): {

ClippedImageImpl.draggableTemplate = (ClippedImageImpl$DraggableTemplate) GWT.create(ClippedImageImpl$DraggableTemplate.class);

}

com.google.gwt.dev.jjs.ast.JBlock

[ERROR] at ClippedImageImpl.java(105): if (ClippedImageImpl.draggableTemplate == null) {

ClippedImageImpl.draggableTemplate = (ClippedImageImpl$DraggableTemplate) GWT.create(ClippedImageImpl$DraggableTemplate.class);

}

com.google.gwt.dev.jjs.ast.JIfStatement

[ERROR] at ClippedImageImpl.java(103): {

if (ClippedImageImpl.draggableTemplate == null) {

ClippedImageImpl.draggableTemplate = (ClippedImageImpl$DraggableTemplate) GWT.create(ClippedImageImpl$DraggableTemplate.class);

}

return ClippedImageImpl.draggableTemplate;

}

com.google.gwt.dev.jjs.ast.JBlock

[ERROR] at ClippedImageImpl.java(103): {

if (ClippedImageImpl.draggableTemplate == null) {

ClippedImageImpl.draggableTemplate = (ClippedImageImpl$DraggableTemplate) GWT.create(ClippedImageImpl$DraggableTemplate.class);

}

return ClippedImageImpl.draggableTemplate;

}

com.google.gwt.dev.jjs.ast.JMethodBody

[ERROR] at ClippedImageImpl.java(103): com.google.gwt.user.client.ui.impl.ClippedImageImpl.getDraggableTemplate()Lcom/google/gwt/user/client/ui/impl/ClippedImageImpl$DraggableTemplate;

com.google.gwt.dev.jjs.ast.JMethod

[ERROR] Compiler returned false

[WARN] recompile failed

[WARN] continuing to serve previous version

On Friday, November 15, 2024 at 4:25:32 PM UTC-5 Colin Alworth wrote:

Could you share the full stack trace of any errors? This exception appears to be truncated. We do have two new, Java17-specific errors, but there isn't enough information here to see if it is related to a known issue.

It might also be helpful to compile for production instead of running in super dev mode - the stack trace is sometimes more useful that way, by giving better context of what was attempting to be compiled.

Can either discuss here briefly or just go ahead and file the issues you've encountered, and we can triage on the issue tracker.

On Friday, November 15, 2024 at 3:20:58 PM UTC-6 B...@lacatena.net wrote:

I switched 2 of my projects from 2.11.0 to 2.12.1, and got an InternalCompilerException error on both when running in Eclipse with the GWT plugin.

Unrelated to that (or maybe it is), I was having another problem I was hoping to get some direction on.  I will post it separately in its own thread, though.

GET /recompile/com.insightxp.i2g.I2g

Job com.insightxp.i2g.I2g_1_0

starting job: com.insightxp.i2g.I2g_1_0

binding: locale=en

binding: user.agent=safari

Compiling module com.insightxp.i2g.I2g

[ERROR] An internal compiler exception occurred

com.google.gwt.dev.jjs.InternalCompilerException: Unexpected error during visit.

at com.google.gwt.dev.jjs.ast.JVisitor.translateException(JVisitor.java:111)

at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:276)

at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:265)

at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:118)

at com.google.gwt.dev.jjs.ast.JCastOperation.traverse(JCastOperation.java:76)

at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361)

On Tuesday, October 29, 2024 at 10:22:14 AM UTC-4 Colin Alworth wrote:

GWT 2.12 is here!

Highlights:

• Added support for Java 12-17 language features, including text blocks, instanceof pattern matching, records, and switch expressions.
• Minimum Java version 11 is required to run any dev tools, though the server code should continue to function with Java 8 for this release. Later versions may no longer support Java 8. Tested to run on Java 11-23.
  
• Added support for sourcemaps to include the contents of the sources files.
• Enabled sourcemaps by default in all browsers
• Fix CSP issues in linkers and dev mode, provide CSP workarounds for GWT-RPC payloads

See https://github.com/gwtproject/gwt/releases/tag/2.12.0 or https://www.gwtproject.org/release-notes.html#Release_Notes_2_12_0 for the complete release notes.

This was a shorter release cycle than we've done in the past, and we're taking steps to simplify some of the processes we use, while still ensuring that projects can continue to update with a minimum of friction. Thanks to our testers, reviewers, committers in this release! A short list of the names that helped bring us this release: Ahmad Bawaneh, Michael S., Dmitrii Tikhomirov, Zbynek Konecny, Paul Kintner, George Paret, Daniel Portmann, Frank Hossfeld, Joan Pablo Gardella, Jens Nehlmeier, Thomas Broyer,

Join us on the issue tracker or at our OpenCollective page to help make future releases.possible.

 

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/5bbca152-0539-413b-92c3-10bf4a991ea7n%40googlegroups.com.