The default customized configuration file may not be usable. In my case (Linux) I had to manually change a few things. I documented the procedure in this wave: http://waveinabox.net/#waveinabox.net/w+LDSm7anj7PA Take a look, maybe it can be extrapolated to a Windows install.
On Tue, Mar 13, 2012 at 19:04, <[email protected]> wrote: > I recently tried and failed to get Wave In A Box building and running on > my Windows Server 2008 R2 64bit virtual machine. I followed all the > instructions in http://www.waveprotocol.org/wave-in-a-box for Windows, > noting the Source Control change to SVN. I then got latest at > https://svn.apache.org/repos/asf/incubator/wave/trunk/ on 3/12/2012 using > TortoiseSVN. I am using the Java SDK jdk1.6.0_31 and WinAnt to do the > builds. I did not install MongoDB which stated it was optional. > > > > The first problem I ran into was a one or more tests failing that > prevented the build from completing. I removed the <junit> tag section to > prevent the tests from running. This completed the build. > > > > First question, has anyone recently gotten this to build on a Windows box? > If so, did you have to do any changes like I did to get it working? If so, > what specifically did you change? > > > > After I got the build working by removing the tests, I ran the Windows > start instructions shown in > http://www.waveprotocol.org/wave-in-a-box/running-wave-in-a-box/running-the-server#windowsbut > starting the server resulted in an exception. The error is: > > > > Exception in thread "main" com.google.inject.CreationException: Guice > creation e > rrors: > > 1) An exception was caught and reported. Message: > 'waveserver_disable_verificati > on' doesn't map to a Boolean object > at > com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:1 > 33) > > 2) Missing constant value. Please call to(...). > at > org.waveprotocol.wave.util.settings.SettingsBinder$3.configure(SettingsBind > er.java:178) > > > > It appears to be a configuration issue, but I'm not sure what I should > change or if its a problem with the build being I built with test failures. > > > > Any help would be appreciated, we are are trying to do this as a proof > that we can stand it up in our Windows infrastrucuture so Linux solutions > are not an option. Thanks! > > > > Brian > -- Saludos, Bruno González _______________________________________________ Jabber: stenyak AT gmail.com http://www.stenyak.com
