"mvn quarkus:dev" workspace discovery should respect default maven profiles

[ge0ffrey]

See second part of discussion here:
https://quarkusio.zulipchat.com/#narrow/stream/187038-dev/topic/ClassLoading.20error.20in.20hot.20deploy

In optaplanner 7.x, the quarkus-school-timetabling-quickstart's "mvn quarkus:dev" was failling because the optaplanner-parent has a maven module that includes the optaplanner-quarkus-integration - and that maven profile is on by default - but Quarkus ignores maven profiles.

@aloubyansky

[quarkusbot]

/cc @quarkusio/devtools

[aloubyansky]

#15342 introduced a config option to enable Quarkus workspace initialization based on effective POMs instead of the "raw" ones, which can be enabled by setting system property quarkus.bootstrap.effective-model-builder to true (e.g. in the surefire and/or quarkus maven plugin config).
The option is not enabled by default because effective POMs take significantly more time to resolve. Which depending on the number of modules in the project and the number of tests, may significantly increase testing time.
Until we find a more efficient alternative though, projects that require it, should enable this option.

[ge0ffrey]

Interesting, thank your for creating this @aloubyansky

How will users know this system property exists? I presume they'll run into the issue and hopefully google the right keywords to end up on a docs page that describes to use quarkus.bootstrap.effective-model-builder?

[aloubyansky]

@ge0ffrey I've added the available options to the end of the maven-tooling guide in this PR #17351