On 20 October 2011 13:42, Ate Douma <[email protected]> wrote: > On 10/20/2011 01:21 PM, Ross Gardler wrote:
... >> >> Assuming there are no objections I will make this happen in time for >> the 0.5 release (unless it is so trivial it's easier for someone else >> to do it, just replace the dependency on the wookie-connector with a >> dependency on Wookie itself and deploy it as appropriate). > > The wookie-connector is a jar which is needed as dependency for the > rave-portal module. You can't use only a dependency on a wookie war for > that. Well duh! Thanks for pointing out what should have been blindingly obvious to me. That saved me some wasted time ;-) > > The wookie war itself must be added as a cargo deployable. Hopefully 'as > is', or otherwise as a minor patched rave-wookie war (using war overlay), > similar to what we do with rave-shindig. > If there is no tweaking/re-configuration needed for Wookie, just adding the > original Wookie war as cargo deployable would be all that is needed. Hmmm.. I have no idea what that means but it does give me a place to start looking in the docs - thanks. Ross > >> >> >> Ross >> On 20 October 2011 10:44, Ate Douma<[email protected]> wrote: >>> >>> Mighty cool Ross! >>> >>> I haven't had the time to try it but will do ASAP. >>> >>> And as a reply on a later message: I'm +1 on bundling Wookie with the >>> demo. >>> I prefer keeping the demo self-contained and not rely or depend on an >>> external server. >>> Current OpenID integration being an exception, but its not required to >>> login >>> any way and its kind of nature of the beast. >>> >>> Bundling Wookie of course should remain optional, as is/should be the >>> case >>> for Shindig. Running Rave with only Wookie integration (bundled or not) >>> should be possible just as well. >>> >>> Ate >>> >>> On 10/20/2011 03:41 AM, Ross Gardler wrote: >>>> >>>> I've finally managed to find the time to complete the Wookie >>>> installation work. Well, the first stage of it at least. Thanks to >>>> Jasha at the hackathon for helping me get back up to speed with how >>>> Rave works these days. >>>> >>>> Currently the location of the Wookie is hard coded to a test server >>>> running in Oxford. Clearly this needs to be customisable. >>>> >>>> I've not added any W3C widgets to user screens by default as this >>>> should still be considered alpha. However, I have added a basic chat >>>> widget to the database. To test it out search for "chat" in the widget >>>> store and add the resulting widget to a page. >>>> >>>> If you log into a different browser or a different machiine with a >>>> different user and add the same widget you can chat across the >>>> browsers. >>>> >>>> Note, this uses a SNAPSHOT Wookie-Connector. Wookie is on target to >>>> release this becore Rave 0.5. However, if it does not manage to do so >>>> we can roll back to the 0.9 release which includes the necessary code. >>>> >>>> Finally, I have a request. Can someone who will be at ApacheCon please >>>> help me set up my dev environment properly. I am a complete Maven >>>> newbie. I can't believe that the development cycle should be as >>>> painful as I'm finding it. >>>> >>> >>> >> >> >> > > -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com
