online-auction-java
online-auction-java copied to clipboard
lagom
Since Lagom `1.5.0-RC1` thhe Kafka Consumer is rather chattier at `INFO` level (with some traces including `\n` chars too (: ). Maybe defaults should be `WARN` for `org.apache.kafka`. Sample: ```...
(some of the following also applies to JUnit 4) - use `assertAll` in Persistent Entity tests with [multiple assertions](https://github.com/lagom/online-auction-java/blob/master/bidding-impl/src/test/java/com/example/auction/bidding/impl/AuctionEntityTest.java#L62-L64) over `outcome` - create and use a [`@Fast` annotation](https://junit.org/junit5/docs/current/user-guide/#writing-tests-meta-annotations) to tag...
As mentioned in https://stackoverflow.com/questions/51262399/lagom-withpathparamserializer, the descriptor for Search Service uses a path param serializer which is unnecessary (https://github.com/lagom/online-auction-java/blob/master/search-api/src/main/java/com/example/auction/search/api/SearchService.java#L23).
Lagom 1.4.5 imported `ReadSideTestDriver` from this project into `lagom-testkit`. The implementation here could be removed. see https://github.com/lagom/online-auction-java/pull/184 and https://github.com/lagom/lagom/milestone/30?closed=1
See https://github.com/lagom/online-auction-scala/issues/69 Thanks @getmetorajesh !
Just run a smoke test using `elasticsearch-6.2.3` and everything seems to work OK. This requires updating: - [ ] docs for installation - [ ] travis jobs (`.deb` , etc...)
Split from https://github.com/lagom/online-auction-java/issues/124
While testing for the version bump to `1.4.1` I noticed the following stacktrace (See below). It doesn't block the normal usage of the application. ``` 14:08:36,489 |-INFO in ch.qos.logback.classic.BasicConfigurator@4de8f0ed -...