Here is a testing multi-module project for migration tests (commit)

If you run the migration with the 3.20 plugin (from the root, by the command

 mvn com.redhat.quarkus.platform:quarkus-maven-plugin:3.20.0.redhat-00002:update -Dstream=3.15

), the result is a failure (in `tools` and `health` modules):

[ERROR] The project state is missing the Quarkus platform BOM 

With older plugin, there is no error when running such command. For example

 mvn com.redhat.quarkus.platform:quarkus-maven-plugin:3.15.4.redhat-00001:update -Dstream=3.15

Note:

• you need to have enabled registry.quarkus.redhat.com

• If any quarkus dependency is added into failing module dependencies. i.e.

          <dependency>
              <groupId>io.quarkus</groupId>
              <artifactId>quarkus-resteasy-jackson</artifactId>
          </dependency> 

  The error does not happen, as the plugin successfully detects the Quarkus BOM.