As Andrej says, there is a permutation for every "axis" you create. One for every browser, one for every locale, one for every other deferred binding axis you use. When you have 4 languages, and use the default support for 4 browsers, you get 16 permutations.
To speed this up during development use only ONE locale, and ONE browser. Then when you need to test, and or deploy, roll that back. To do this use the <set-property> element in your module (as opposed to just extend-property). For example: <set-property name="user.agent" value="gecko" /> Also, make sure you give the compiler a lot of memory (the -Xmx switch to the JVM), and try to make sure you use a server VM (-server, depending on your platform and OS version you may or may not get a - server by default). On Sep 16, 6:21 am, Bal Krishna <[EMAIL PROTECTED]> wrote: > Hi All, > I am implementing I18 support for my application and I am using GWT > I18 support. > In my module file, I extended three locales and compilation time for > my java files increased drastically. Earlier it was taking around > 30-40 mins but after adding three locales in my module configuration > file it is taking around 120-130 mins. > I am very surprised by seeing this much difference in compilation > time. Why is it so?? > Is there any mistake I made in adding support of locale to my > application or something wrong with handling of I18 by GWT API?? > Can anyone help me out?? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
