@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
@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
quired 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
>>>> > ...
>>
t;> 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
>&
he 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 m
@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
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
s. 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 - F
st 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
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
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
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
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
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
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
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
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 dia
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
day, 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 whe
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
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] ---
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
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
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
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
ps://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. Ju
> 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:
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
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
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
>&
@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
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
> 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:
>&
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:
...
...
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:
>
>
wt.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:
> Tha
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
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
38 matches
Mail list logo
