Figured it out, I should just run ant. Guess running compile and compile_gwt does not update the jar files :-)
On Sat, Oct 2, 2010 at 6:32 PM, Matt Richards <[email protected]> wrote: > I normally update using "hg pull -u", this should take care of both pulling > and updating. > then I run ant clean, and ant compile compile_gwt. I've deleted my dist > folder and will rebuild now and see what happens.. > > > On Sat, Oct 2, 2010 at 6:24 PM, Joseph Gentle <[email protected]> wrote: > >> You are using an old version of the code / a build of an old version >> of the code. Did you do 'hg update' after 'hg pull'? Did you rebuild? >> >> -J >> >> On Sun, Oct 3, 2010 at 10:10 AM, Matt Richards <[email protected]> >> wrote: >> > INFO: An exception was caught and reported. Message: >> > java.lang.RuntimeException: Invalid account store type: 'fake' >> > java.lang.RuntimeException: Invalid account store type: 'fake' >> > at >> > >> org.waveprotocol.wave.examples.fedone.persistence.PersistenceModule.bindAccountStore(PersistenceModule.java:110) >> > at >> > >> org.waveprotocol.wave.examples.fedone.persistence.PersistenceModule.configure(PersistenceModule.java:76) >> > at com.google.inject.AbstractModule.configure(AbstractModule.java:59) >> > at >> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:223) >> > at com.google.inject.spi.Elements.getElements(Elements.java:101) >> > at >> > >> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:135) >> > at >> > >> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:113) >> > at >> > >> com.google.inject.internal.InjectorImpl.createChildInjector(InjectorImpl.java:186) >> > at >> > >> com.google.inject.internal.InjectorImpl.createChildInjector(InjectorImpl.java:193) >> > at >> org.waveprotocol.wave.examples.fedone.ServerMain.run(ServerMain.java:60) >> > at >> org.waveprotocol.wave.examples.fedone.ServerMain.main(ServerMain.java:50) >> > Exception in thread "main" com.google.inject.CreationException: Guice >> > creation errors: >> > 1) An exception was caught and reported. Message: Invalid account store >> > type: 'fake' >> > at >> > >> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:135) >> > 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.wave.examples.fedone.ServerMain.run(ServerMain.java:60) >> > at >> org.waveprotocol.wave.examples.fedone.ServerMain.main(ServerMain.java:50) >> > Caused by: java.lang.RuntimeException: Invalid account store type: >> 'fake' >> > at >> > >> org.waveprotocol.wave.examples.fedone.persistence.PersistenceModule.bindAccountStore(PersistenceModule.java:110) >> > at >> > >> org.waveprotocol.wave.examples.fedone.persistence.PersistenceModule.configure(PersistenceModule.java:76) >> > at com.google.inject.AbstractModule.configure(AbstractModule.java:59) >> > at >> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:223) >> > at com.google.inject.spi.Elements.getElements(Elements.java:101) >> > at >> > >> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:135) >> > at >> > >> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:113) >> > ... 4 more >> > When I set it to use fake.. >> > On Sat, Oct 2, 2010 at 5:43 PM, Joseph Gentle <[email protected]> >> wrote: >> >> >> >> Er, the fake user store should be supported, although like waves, >> >> users aren't saved between sessions yet. >> >> >> >> We haven't added account creation yet. That should be coming this week. >> >> >> >> -J >> >> >> >> >> >> On Sun, Oct 3, 2010 at 8:09 AM, Matt Richards <[email protected]> >> wrote: >> >> > fake storage does not appear to be supported on the current tip. >> >> > Is there another change that supports account creation that I'm not >> >> > aware >> >> > of? >> >> > >> >> > On Wed, Sep 29, 2010 at 2:06 AM, Joseph Gentle <[email protected]> >> >> > wrote: >> >> >> >> >> >> I'm about to submit a change which makes the little login box in the >> >> >> web client actually authenticate the user properly, logging in with >> >> >> the requested username and an empty password. >> >> >> >> >> >> If you don't have an account on your server, you can no longer log >> in >> >> >> and mess about. And its currently impossible to create accounts, so >> >> >> that is a bit of a problem. For the time being, I've made an account >> >> >> store which creates accounts for people on the fly, with an empty >> >> >> password. This account store will be removed once account management >> & >> >> >> persistence has been added to the server. >> >> >> >> >> >> If you have a custom configuration file, put this at the bottom of >> >> >> run-config.sh: >> >> >> >> >> >> ACCOUNT_STORE_TYPE=fake >> >> >> >> >> >> If you're using the old default (ACCOUNT_STORE_TYPE=memory), you >> will >> >> >> not be able to log in. >> >> >> >> >> >> If you haven't made your own configuration file, no action is >> >> >> necessary. >> >> >> >> >> >> Cheers >> >> >> Joseph >> >> >> >> >> >> -- >> >> >> 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%[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]<wave-protocol%[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]<wave-protocol%[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]<wave-protocol%[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]<wave-protocol%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/wave-protocol?hl=en. >> >> > > > -- > --Matt > -- --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.
