Oops! Well, I applied your websocket backport patch from the other thread and compiled on Hardy (The errors in another module killed Diablo.) So I don't have the cross-browser websocket support etc.
I'm still running a tweaked io2010! But it's finally up and running, you can log in at http://wave.geekchique.org - use a geekchique.org wave address! On 13 June, 02:21, Tad Glines <[email protected]> wrote: > Your problem is that you pulled from the io2010 clone. My fixes and web > socket changes are in my clone of io2010. You need to pull > tadglines-websockets.googlecode.com/hg/ > > -Tad > > On Jun 12, 2010, at 5:33 PM, Graham Simpson <[email protected]> > wrote: > > > > > I thought it was odd that I had the same issue on FreeBSD/OpenJDK > > 1.6.. > > > Ok, retrying now: > > > hg clonehttps://io2010.wave-protocol.googlecode.com/hg/wave-protocol- > > io2010 > > cd wave-pr* > > ant all > > > Result: > > > Buildfile: build.xml > > > init: > > [mkdir] Created dir: /usr/home/gray001/wave-protocol/wave-protocol- > > io2010/build/core > > [mkdir] Created dir: /usr/home/gray001/wave-protocol/wave-protocol- > > io2010/build/gwt > > [mkdir] Created dir: /usr/home/gray001/wave-protocol/wave-protocol- > > io2010/build/test > > [mkdir] Created dir: /usr/home/gray001/wave-protocol/wave-protocol- > > io2010/build/instr > > [mkdir] Created dir: /usr/home/gray001/wave-protocol/wave-protocol- > > io2010/dist > > [mkdir] Created dir: /usr/home/gray001/wave-protocol/wave-protocol- > > io2010/build/staging > > [mkdir] Created dir: /usr/home/gray001/wave-protocol/wave-protocol- > > io2010/build/testoutput > > [mkdir] Created dir: /usr/home/gray001/wave-protocol/wave-protocol- > > io2010/www > > > proto_compile: > > [javac] Compiling 4 source files to /usr/home/gray001/wave- > > protocol/wave-protocol-io2010/build/core > > > compile: > > [javac] Compiling 888 source files to /usr/home/gray001/wave- > > protocol/wave-protocol-io2010/build/core > > [javac] /usr/home/gray001/wave-protocol/wave-protocol-io2010/src/ > > org/waveprotocol/wave/client/common/util/JsoStringMap.java:65: type > > parameters of <V>V cannot be determined; no unique maximal instance > > exists for type variable V with upper bounds V,java.lang.Object > > [javac] return backend.getObjectUnsafe(key); > > [javac] ^ > > [javac] /usr/home/gray001/wave-protocol/wave-protocol-io2010/src/ > > org/waveprotocol/wave/client/common/util/JsoStringMap.java:72: type > > parameters of <V>V cannot be determined; no unique maximal instance > > exists for type variable V with upper bounds V,java.lang.Object > > [javac] return backend.getObjectUnsafe(key); > > [javac] ^ > > [javac] /usr/home/gray001/wave-protocol/wave-protocol-io2010/src/ > > org/waveprotocol/wave/client/common/util/JsoStringMap.java:80: type > > parameters of <V>V cannot be determined; no unique maximal instance > > exists for type variable V with upper bounds V,java.lang.Object > > [javac] return backend.getObjectUnsafe(escape(key)); > > [javac] ^ > > [javac] /usr/home/gray001/wave-protocol/wave-protocol-io2010/src/ > > org/waveprotocol/wave/model/document/util/LineContainers.java:157: > > incompatible types > > [javac] found : > > org.waveprotocol.wave.model.document.util.Point.El<java.lang.Object> > > [javac] required: > > org.waveprotocol.wave.model.document.util.Point<N> > > [javac] return Point.inElement(el, nodeAfter); > > [javac] ^ > > [javac] Note: Some input files use or override a deprecated API. > > [javac] Note: Recompile with -Xlint:deprecation for details. > > [javac] Note: Some input files use unchecked or unsafe operations. > > [javac] Note: Recompile with -Xlint:unchecked for details. > > [javac] 4 errors > > > BUILD FAILED > > /usr/home/gray001/wave-protocol/wave-protocol-io2010/build.xml:126: > > Compile failed; see the compiler error output for details. > > > Total time: 33 seconds > > > On Jun 12, 11:08 pm, Tad Glines <[email protected]> wrote: > >> Hmmm, It compiled fine for me on my Ubuntu 8.04 system. > > >> On Sat, Jun 12, 2010 at 2:49 PM, Graham Simpson <geekchique.org@ > > >> googlemail.com> wrote: > >>> Tad - that's brilliant, thankyou - although I can't compile any more > >>> on either Ubuntu Hardy or on FreeBSD 8.0 - I'll have another look > >>> after work tomorrow. > > >>> On Jun 12, 2:09 pm, Tad Glines <[email protected]> wrote: > >>>> tar cvf wave.tar *.sh *.example dist etc war www > > >>>> -Tad > > >>>> On Sat, Jun 12, 2010 at 4:07 AM, Graham Simpson <geekchique.org@ > > >>>> googlemail.com> wrote: > >>>>> Hello - sorry I haven't got back earlier, it's been a busy week at > >>>>> work and the HackerSpace! > > >>>>> I've got the system build on my Ubuntu Dev Server - my question is > >>>>> rather - which files do I need to copy onto my production server to > >>>>> run the system? (I compile on Ubuntu Lucid, but my live server is > >>>>> Solaris 10 on a Sun Fire.) I'd rather not take the entire source tree > >>>>> over to the web server if it's not necessary.. I'm afraid I'm finding > >>>>> the build structure a little confusing! (I am but a simple sysadmin.) > > >>>>> Thanks again, > >>>>> Gray. > > >>>>> On Jun 6, 12:54 am, James Purser <[email protected]> wrote: > >>>>>>> Hello! > > >>>>>>> I note that Collaborynthwave and eggywave are down at the moment - > >>> I'm > >>>>>>> in the process of getting io2010 rolled out onto the GeekChique > >>> wave > >>>>>>> server - but it's inevitably slow progress. > > >>>>>> Ah sorry about that, collaborynth should be be back up now. > > >>>>>>> Thing is - I'm really stupid - I've successfully compiled the > >>> server, > >>>>>>> but which components do I actually need to run the new service? > >>>>>>> Specifically, which files from the build directory? All of them? > >>> Since > >>>>>>> I'm not compiling on my target server (Solaris 10/Sparc64) but on > >>> my > >>>>>>> Ubuntu/x86 web server I'd like to minimise the clutter I transfer. > > >>>>>> The best way to ensure that everything is built is to use the > >>> command: > > >>>>>> $: ant all > > >>>>> -- > >>>>> 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]<wave-protocol%2bunsubscr...@goog > >>>>> legroups.com> > >>> <wave-protocol%2bunsubscr...@goog legroups.com> > >>>>> . > >>>>> 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]<wave-protocol%2bunsubscr...@goog > >>> legroups.com> > >>> . > >>> 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 > > athttp://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.
