Changing to saving next beat rather than last beat because it makes it easier for...
authormyrle-krantz <mkrantz@mifos.org>
Thu, 18 May 2017 21:44:24 +0000 (23:44 +0200)
committermyrle-krantz <mkrantz@mifos.org>
Thu, 18 May 2017 21:44:24 +0000 (23:44 +0200)
commita697d900caaafc561e96368e7f0aae5a282bec9c
tree98cbd299ba74aac0b4498a838c645c4a6ad605f7
parent17be673e31583cd717171f80e33d3440357b8db4
Changing to saving next beat rather than last beat because it makes it easier for me to separate checking beats for publishing from persisting the beat.  I need to separate these two things because I cannot mock or spy on a class annotated with @Transactional.
component-test/src/main/java/io/mifos/rhythm/TestBeats.java
service/src/main/java/io/mifos/rhythm/service/internal/mapper/BeatMapper.java
service/src/main/java/io/mifos/rhythm/service/internal/repository/BeatEntity.java
service/src/main/java/io/mifos/rhythm/service/internal/scheduler/Drummer.java
service/src/main/resources/db/migrations/mariadb/V1__initial_setup.sql
service/src/test/java/io/mifos/rhythm/service/internal/scheduler/DrummerTest.java