Evolutions not run property on play 2.8

I have just migrated from play 2.6 and an older version of play-ebean plugin to play 2.8 and version 6.0.0 of this plugin

We have noticed a change of behavior when running evolutions on a dev server

Previous behavior on a working app

1. Change a model in any way (let's assume that we change the name of a property)
2. Starting the app notifies the developer that an evolution has to be run
3. Pressing the apply button results in possibly another error (inconsistent state), and marking the problem as resolved causes the entire database to be deleted and recreated with the new schema

Current behavior

1. Pressing the apply button notifies of an inconsistent state
2. Continuing to press the button reloads the same page
3. After some reloads the max url limit is reached

In the end what i would like to achieve is that when ebean generates a different schema, the entire database is deleted and recreated accordingly.

Start by reproducing the migration from Play 2.6 and the older play-ebean plugin to Play 2.8 with play-ebean 6.0.0. Trace the development evolution apply flow when Ebean generates a different schema, especially the inconsistent-state reload loop. Done means the development database is deleted and recreated with the new schema.