latos / wave-protocol

Automatically exported from code.google.com/p/wave-protocol
0 stars 0 forks source link

Could not find a suitable constructor #177

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. clone repo
2. build sources
3. ./run-server.sh

What is the expected output? What do you see instead?
Server is running without any issues, however it crashes with exception:
# ./run-server.sh 
Exception in thread "main" com.google.inject.CreationException: Guice creation 
errors:

1) Could not find a suitable constructor in 
org.waveprotocol.box.server.waveserver.DeltaStoreBasedWaveletStore. Classes 
must have either one (and only one) constructor annotated with @Inject or a 
zero-argument constructor that is not private.
  at org.waveprotocol.box.server.waveserver.DeltaStoreBasedWaveletStore.class(DeltaStoreBasedWaveletStore.java:213)
  at org.waveprotocol.box.server.waveserver.WaveServerModule.configure(WaveServerModule.java:94)

1 error
    at com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:385)
    at com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:164)
    at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:116)
    at com.google.inject.internal.InjectorImpl.createChildInjector(InjectorImpl.java:186)
    at com.google.inject.internal.InjectorImpl.createChildInjector(InjectorImpl.java:193)
    at org.waveprotocol.box.server.ServerMain.run(ServerMain.java:98)
    at org.waveprotocol.box.server.ServerMain.main(ServerMain.java:69)

What version of the product are you using? On what operating system?
- head from repo
- Linux

Please provide any additional information below.
Checked twice within different Linux environment (ArchLinux and Ubuntu), the 
same problem occurs.

Original issue reported on code.google.com by mm.piet...@gmail.com on 3 Dec 2010 at 10:52

GoogleCodeExporter commented 8 years ago
This should be fixed in revision 07e0ae3086, which was pushed a few minutes 
ago. Please pull that revision and, if the problem persists, reopen this issue.

Original comment by so...@google.com on 3 Dec 2010 at 10:58