Do you mean you are getting only one .nocache.js file even if you have "gwtc" target for each module? If you have proper rename-to attribute for each module in the <module>.gwt.xml files, then the gwtc target for the particular module will generate appropriate .nocache.js file.
-Venkatesh On Wed, Mar 17, 2010 at 3:26 PM, jbdhl <[email protected]> wrote: > Thanks. But my question was more about how to actually specify that > multiple nocache.js files should be created. If I just create > MyApp1.gwt.xml and MyApp2.gwt.xml, then still only one nocache.js file > is created when I compile. It doesn't help if I specify multiple entry > points within a single MyApp.gwt.xml either. So guess I miss something > in order for the GWT compiler to recognize that it should generate > multiple nocache.js files. > > I have failed to locate an example on a multiple entry point > implementation out there. > > -- > 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]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- 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.
