One workaround that just came to my mind: because code does not run in Java (prod mode), you don't need to run tests with Java assertions enabled (i.e. remove -ea from JVM arguments); GWT assertions are governed by an -ea flag in -Dgwt.args=, independent from the -ea flag of the JVM. HTH.
On Tuesday, February 14, 2017 at 5:57:43 PM UTC+1, Daniel Kln wrote: > > Thank you thomas, caused by your hint i could find the mistake. > > in my gwt.xml file i added a block comment around: > > <!-- <extend-property name="locale" values="de" /> > <extend-property name="locale" values="en" />--> > > this solved the problem. > > Am Dienstag, 14. Februar 2017 11:52:33 UTC+1 schrieb Daniel Kln: >> >> Hi, >> >> i setted in the run config the arg: -Dgwt.args="-runStyle Manual:1". >> >> When i start running the gwt unit test, i get a link, which i have to >> paste into a browser of my choice. This is what i expected. But than the >> browser shows: >> Development Mode requires the GWT Developer Plugin >> >> My question: how i can avoid this problem. In production mode the same >> result appears. >> >> Thank you a lot for your help >> >> Daniel >> >> > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
