Re: Code splittingmysteries

Yes, I understand what you mean, I experienced the same... 

It's hard to hand over a "test case" that fails, to the dev team, such that they can use that to work on :(

Yes it would be nice to have better  facilities such that we can try to track done the cause our self. Currently the SOYC report isn't helping a lot. 

To my experience the SOYC report is buggy, as some pages result in a 404 :(.. (I experienced that several times the last years with a correctly created soyc, it's also in some issue if I remember correctly).

On Wed, Jun 12, 2013 at 4:45 PM, James Horsley <james.horsley@gmail.com> wrote:

Yeah. I've tried reproducing the issue with a sample app but thus far haven't been able to; not sure that the sample webapp captures enough of the complexity of the actual webapp we're having the problem with. As I mentioned before can confirm that changing none of the webapp code but switching between 2.5 and 2.5.1 causes everything to end up in the leftover. From the compiler report it's not at all obvious why these classes are in the leftover fragment as they look isolated from what I can tell.

On 12 June 2013 13:13, Ed <post2edbras@gmail.com> wrote:

Ed, did you ever get this sorted? As I commented on the linked issue I'm running into what seems to be a similar problem.

No. It's hard to track the exact cause. It tried, but had to give up (a lot of time, and not knowing exactly what happens.

But it's good to see that more people are experiencing the same kind of problems such that I am not alone ;)

Ray seem to be the code splitting guru. Let's hope he has has some time to look at this ;)

If you can isolate the problem in a small program that reproduces this behavior, please do upload it in the issue. I tried, but failed :(

This will help the gwt dev team a lot to solve the problem (and the issue will get a higher priority and solved sooner).

--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to a topic in the Google Groups "Google Web Toolkit" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/_8CdVbBb488/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, 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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.