The mappings file only reports what was going on in the compile phase,
so modifying it has no effect.
You have to set specific values for your properties in the module.xml files:
e.g.
>>
<set-property name="user.agent" value="safari"/>
<<
SDM picks this change up I believe without restart. However to see the
change in the mappings file too, you have to clean and recompile (i.e.
start your devserver).
On 04/12/14 15:02, Rob Walker wrote:
I'm seeing this file in the artefacts generated by the SDM compile in
the temp dir. Isn't editing this file only going to apply to the
current invocation though?
Presumably next time around it's going to get a different temp dir,
and this fill will get recreated again.
Have to confess - I don't fully follow what this file does though, and
why we need to manually edit it
On Thursday, 4 December 2014 15:54:48 UTC+2, Robert Hoffmann wrote:
@thomas
thank you, that helped me to reduce the permutations to one.
For the record, compilation-mappings.txt contained multiple
cache.js file entries, now it only contains one
>>
FC8BCE744D2BA8E0C463CE0D2F389DB7.cache.js
Devmode:devmode.js
<<
...and now sdm works.
And it's fast :-)
On Thursday, December 4, 2014 10:15:36 AM UTC+1, Robert Hoffmann
wrote:
Hi,
Is there a way to see which properties cause the permutations?
(I'm using GWT 2.7.0)
When compiling your project, you should have
a compilation-mappings.txt file generated next to the *.nocache.js.
--
You received this message because you are subscribed to the Google Groups "GWT
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/54806A58.9070203%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
