Tim Marcus Moore

Java doesn't provide a great way to deal with naming conflicts. In Scala you can use relative package names, or import with an alias, but in Java if you have...

Here's what I'm thinking now... would love to hear others' thoughts on this. - Keep the API response type names simple nouns (like they are now) `Item`, `User`, etc. -...

Related: #15 ... sounds like @ignasi35 and I share some thoughts.

I don't know if we really need to worry too much about JSON evolutions/migrations at this stage. This is really a pre-1.0 thing.

That's a good point, but I think we can be deliberate with our choice of examples for JSON migration, to ensure they're easy for people to understand. Maybe this _is_...

Will this require use of the optional serializer?

This has caused some failures in Travis CI as well: https://travis-ci.org/lagom/online-auction-scala/builds/208863419

The Java tests pass, but with an error logged: ``` [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 Auction....

That error is logged with clean data too, though, so it must be unrelated to this issue.

Oh right... strange that it printed after the next test started. Are we missing an await?