The solution that worked for me was to move the code from the runAsync method of split point 1 out of the runAsync call (next to it). This put the relevant code into the initial download part, where I could trace the dependency.
On Monday, October 14, 2013 1:00:41 PM UTC-4, Ben Klein wrote: > > In my GWT application, I have several split points. In the compile report, > it says that a certain class has some code loaded in split point 1 and some > code loaded in split point 5. How do I find out what is causing the code to > load from split point 5? > -- 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+unsubscr...@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/groups/opt_out.
