Re: Testing native @JsType in GWT tests

Thanks, Thomas. Changing to production mode fixed the problem. However, I noticed that when using production mode in tests, I cannot test the type-matching for JSNI anymore. Previously, the GWT generated interface code caught the problem at runtime in development mode. When running in production

Re: GWT with App Engine (standard) and maven?

On Monday, March 12, 2018 at 12:55:22 PM UTC+1, dflorey wrote: > > Hi folks, > after all those years I've decided to start migrating our GWT / App Engine > (standard) projects from Ant to Maven. > The main app consists of several GWT libraries and multiple modules. > I'd also like to split the

Re: GWT with App Engine (standard) and maven?

Hey Thomas, Thanks for your instant reply! I've been thinking about Gradle (as I'm new to both) as well, but I need a bunch of Google tools (like Cloud Endpoints) which come with a Maven plugin. So I thought it would be easier to go with Maven (?). Thanks for the link to the sample app! It is

Re: Testing native @JsType in GWT tests

On Monday, March 12, 2018 at 9:17:58 AM UTC+1, Mincong Huang wrote: > > Thanks, Thomas. Changing to production mode fixed the problem. > > However, I noticed that when using production mode in tests, I cannot test > the type-matching for JSNI anymore. Previously, the GWT generated interface >

GWT with App Engine (standard) and maven?

Hi folks, after all those years I've decided to start migrating our GWT / App Engine (standard) projects from Ant to Maven. The main app consists of several GWT libraries and multiple modules. I'd also like to split the monolithic app into several "microservices" running on App Engine (frontend

Re: GWT with App Engine (standard) and maven?

This is the pom.xml that I've got so far: http://maven.apache.org/POM/4.0.0; xmlns:xsi= "http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd;> 4.0.0 xxx-appengine com.floreysoft.xxx

Re: Testing native @JsType in GWT tests

I tried the -ea flag (checkAssertions in the POM). It seems to be incompatible with the flag productionMode. I guess when production mode is true, assertions are disabled. I ended up with two test executions in my POM: "jsni-test" for keeping the type checked for legacy JSNI codes, and

Re: GWT with App Engine (standard) and maven?

I tried to leverage your archetypes to get the gwt part (without appengine) running as a starting point. What I did: I created a maven project from the archetype (using the eclipse maven wizard). I can see a nice multi-module project client/shared/server in my workspace. As per your suggestion I

Re: GWT with App Engine (standard) and maven?

On Monday, March 12, 2018 at 2:10:46 PM UTC+1, dflorey wrote: > > I tried to leverage your archetypes to get the gwt part (without > appengine) running as a starting point. > What I did: > I created a maven project from the archetype (using the eclipse maven > wizard). > I can see a nice

How to pass a build number to a gwt app?

hi, I would like my gwt app to be able to identify its version itself, by providing a method that returns the build number. I'm using Jenkins, maven and the maven plugin for gwt to build my app. Jenkins generates the build number and I know how to

passing the logLevel in the URL is it possible to retrieve the level inside GWT?

We want to enable debugging when pass the appropriate level with the URL. The problem is that we use web workers and logging in the web worker does not work with the GWT loggers. I want to pass the logLevel to the worker as parameter and then log inside the worker accordingly. Can I retrieve

How to pass a build number to a gwt app?

Easiest with recent GWT version would be to declare a , get it using System.getProperty(), and set it with --property. With older versions, use Maven filtering on a properties file you use with a com.google.gwt.i18n.client.Constants; or have a look at Mojo's Java template plugin. -- You