Ignasi Marimon-Clos

I think that stacktrace is expected: ``` [info] Test com.example.auction.item.impl.ItemServiceImplIntegrationTest.shouldFailEditOnBiddingFinished started [info] Test com.example.auction.item.impl.ItemServiceImplIntegrationTest.shouldEmitItemUpdatedEvent started [error] item - Exception in RestCallId{method=PUT, pathPattern='/api/item/:id'} com.lightbend.lagom.javadsl.api.transport.TransportException: Can't update an item of a completed...

I don't think we're missing an await. I think it's a race condition when the logging. I'm not sure if the stack trace is printed by the server-side code or...

Yes, I _think_ a reload is necessary. I think I saw it consistently and the only difference compared to other times I worked on `online-auction` is that I was changing...

Thanks @2beaucoup for reporting!

The solution to handle multi-repo with Lagom is not demo-ed so it'd be good if we found a way. Maybe having two folders in the root of this repo where...

I think the example in the PR is quite illustrative: https://github.com/lagom/lagom/pull/763/files#diff-69be132232784c54f9b1cdfc434186af I would build from that: 1. if the folder `target/elasticsearch-5.0.2` doesn't exist, download and unzip there 2. don't check...

I think we can do that on a separate PR.

Hi @lakhina the feature is only available in `master` which means you will only see it if you compile lagom locally and make your PR depend on `1.4.0-SNAPSHOT`.

This will not be mergeable until `1.4.0` is out, but in the meantime you can clone `lagom/lagom` and use `publishLocal` in sbt to test your changes. ;-)

Few maintenance tasks (e.g. adding headers #9) will be better completed in `sbt` sot it'd be great to complete them before working on this sbt-to-maven conversion.