The gwt-site-webapp also has such configuration; it's used for the
menu/navigation at http://www.gwtproject.org
https://gwt.googlesource.com/gwt-site-webapp (see pom.xml and *.gwt.xml files)
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsu
https://github.com/ibaca/rxcanvas-gwt 😅
On Thursday, November 16, 2017 at 12:08:44 AM UTC+1, Ignacio Baca
Moreno-Torres wrote:
>
> FYI this project is a working example of deploying a gwt app with source
> maps. The pom is configured to included both the source map and the java
> sources. I use
FYI this project is a working example of deploying a gwt app with source
maps. The pom is configured to included both the source map and the java
sources. I use site.sh to deploy as a github page.
On Wednesday, November 15, 2017 at 9:40:26 PM UTC+1, AJ wrote:
>
> Thanks Colin.
> That look like e
Thanks Colin.
That look like exactly what I need.
This will be a 'production' url we use to debug the issue and then
re-deploy the 'real' build once we have stepped the code and found the
offending null point.
Nice to know about the stack trace.
Thank you very much for the very detailed reply.
Symbol maps are distinct from source maps, the serve different purposes.
Sourcemaps, when deployed with your actual source, allow the browser to ask
the server for your Java source, so you can see if when you debug - this
may not be something most production applications want their customers to
Hello,
I have an issue that only manifests in a deployed GWT application and so am
trying to enable source maps in the production build.
I have added...
...to the project.ui.xml file and have passed -saveSource to the compiler
In my war I see the WEB-INF/deploy/ProjectName/symbolMaps
