I solved it different way as I would not be allowed to switch to bridged (the network admin would not be too amused).
In the end I set the bindAddress to 0.0.0.0, this means that the superdev mode is bound to my virtual machines host name, I then added a rule in the windows hosts file.
the source maps are now available ;-)
On Tuesday, 17 March 2015 13:36:33 UTC+1, Jens wrote:
-- In the end I set the bindAddress to 0.0.0.0, this means that the superdev mode is bound to my virtual machines host name, I then added a rule in the windows hosts file.
the source maps are now available ;-)
On Tuesday, 17 March 2015 13:36:33 UTC+1, Jens wrote:
I don't think that you can change it for now. Maybe via a custom linker, not sure, but that would be a bit more work anyways.As a workaround you can reconfigure your VM so you can directly access it without forwarding, e.g. use a bridge instead of NAT.-- J.
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment