Alas, changing the property in the java and .gwt.xml to "my.locale" does
not result in less incorrect code:
unflattenKeylistIntoAnswers(['en'],
'85A0B45105661378F351C4FA6230BF99');
unflattenKeylistIntoAnswers(['es'],
'85A0B45105661378F351C4FA6230BF99');
unflattenKeylistIntoAnswers(['fr'],
'85A0B45105661378F351C4FA6230BF99');
unflattenKeylistIntoAnswers(['en'],
'85A0B45105661378F351C4FA6230BF99' + ':1');
unflattenKeylistIntoAnswers(['es'],
'85A0B45105661378F351C4FA6230BF99' + ':1');
unflattenKeylistIntoAnswers(['fr'],
'85A0B45105661378F351C4FA6230BF99' + ':1');
unflattenKeylistIntoAnswers(['en'],
'85A0B45105661378F351C4FA6230BF99' + ':2');
unflattenKeylistIntoAnswers(['es'],
'85A0B45105661378F351C4FA6230BF99' + ':2');
unflattenKeylistIntoAnswers(['fr'],
'85A0B45105661378F351C4FA6230BF99' + ':2');
strongName = answers[computePropValue('my.locale')];
Seems like a good thought though. If there are side effects to reusing
those property strings, then those two extend-configuration-property tags
should be moved to I18n.gwt.xml and UserAgent.gwt.xml so that User-less GWT
code can be written that will be compatible with J2CL.
Anyone else got a hint? Should I just file this as a bug and insert some
lame replace-with rules to fool the compiler for the time being? Is this
really not actually tested even though it is the "correct" way to manage
properties now?
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/142c1ee8-534b-4118-af1c-9eda51bd3f80%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
