@ChangeSet executed before @ChangeUnit, ignoring order about mongock

[dieppa]

Hello @EfreetSK , this seem an important one. We'll take a look shortly.

[osantana85]

Hello @EfreetSK , after review your provided project and the Mongock's current behaviour, the fix for your project is setting the order in the legacy @ChangeLog annotation, this way:

@ChangeLog(order = "0001")
public class DatabaseChangeLog {
    @ChangeSet(order = "0001", id = "0001", author = "test")
    public void myFirstChangeLog(MongoDatabase db) {
        db.createCollection("helloMongock");
    }
}

Note that the order should be lower than the order of your new @ChangeUnit classes (alphabetical order).

If you have multiple ChangeLog classes, please ensure that you set the order attribute in all of them.

Please let us know if it works for you.

We will update documentation to clarify the upgrade to v5 guide.

Many thanks.

[EfreetSK]

@osantana85 Thank you for your reply. You're right, setting the order of @ChangeLog solves my issue, thank you!

Maybe for others who are reading this, I was wondering what should be the order of @ChangeUnit if there are multiple @ChangeSets. So f.e. let's have a @ChangeLog like this

@ChangeLog(order = "0001")
public class DatabaseChangeLog {
    @ChangeSet(order = "0001", id = "0001", author = "test")
    public void myFirstChangeSet(MongoDatabase db) {
        db.createCollection("helloMongock");
    }

    @ChangeSet(order = "0002", id = "0002", author = "test")
    public void mySecondChangeSet(MongoDatabase db) {
        db.createCollection("mySecondCollection");
    }
}

And I was wondering what should be the @ChangeUnit order now, 0002 (as a second class to be executed) or 0003 (as a third 'change set' to be executed). I tried it and the answer is 0003

@ChangeUnit(id="0003", order = "0003", author = "test")
public static class MyFirstChangeUnit {