No worries :) That's what we're here for (us who live on the edge are going to get cut sometime ;))
James Purser On Thu, Jun 10, 2010 at 11:31 AM, Anthony Baxter <[email protected]> wrote: > Yeah, sorry about that guys - mea maxima culpa. I'll try to get it all > fixed up today. > > > On Thu, Jun 10, 2010 at 11:22, Matt Richards <[email protected]> wrote: >> These jetty patches included in your patch (I too use the dev channel >> for chrome)? >> And I prematurely jumped on the compile_gwt, the failure is there but >> from your comments I won't worry. >> >> On Wed, Jun 9, 2010 at 8:14 PM, Tad Glines <[email protected]> wrote: >>> I tried it on a clean clone of io2010 and it build fine. You will get an >>> error about JavaRegExp.java but you can ignore it because that class isn't >>> used anywhere yet. >>> You should see 15 permutations compiled. >>> >>> You might want to try this set of commands: >>> ant clean >>> ant >>> ant compile_gwt >>> >>> I found that the dev channel version of chrome updated their websocket code >>> to the version 76 protocol and the jetty verison in wave only supports >>> websocket protocol verison 75. >>> I found that the latest version i the jetty source repo has the updates and >>> when I patched the wave version of jetty with those files it worked with the >>> dev channel version of chrome. >>> >>> -Tad >>> >>> On Wed, Jun 9, 2010 at 5:52 PM, Matt Richards <[email protected]> wrote: >>>> >>>> compile_gwt fails with this patch applied :( >>>> >>>> On Wed, Jun 9, 2010 at 5:49 PM, James Purser <[email protected]> >>>> wrote: >>>> > Hi Tad, >>>> > >>>> > I'll give the patch a go, thanks. >>>> > >>>> > I've also submitted the original email as an issue so if you want to >>>> > attach the patch there that would be great :) >>>> > >>>> > http://code.google.com/p/wave-protocol/issues/detail?id=95 >>>> > >>>> > James Purser >>>> > >>>> > -- >>>> > You received this message because you are subscribed to the Google >>>> > Groups "Wave Protocol" 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/wave-protocol?hl=en. >>>> > >>>> > >>>> >>>> >>>> >>>> -- >>>> --Matt >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "Wave Protocol" 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/wave-protocol?hl=en. >>>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Wave Protocol" 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/wave-protocol?hl=en. >>> >> >> >> >> -- >> --Matt >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Wave Protocol" 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/wave-protocol?hl=en. >> >> > > > > -- > Anthony Baxter, [email protected] > > -- > You received this message because you are subscribed to the Google Groups > "Wave Protocol" 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/wave-protocol?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Wave Protocol" 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/wave-protocol?hl=en.
