Dev-Loop fails when fullBuild does execute compiler:compile

[romain-grecourt]

Version: 4.0.2

---

If the helidon-cli-maven-plugin is configured to have a life-cycle for the full build that does not include compiler:compile then the dev-loop fails with:

loop failed helidon-cli-maven-plugin must be configured as an extension

See MavenProjectSupplier.

TLDR: the dev-loop relies on a mechanism (MavenLifecycleParticipant) that only works within Maven extensions. It uses the event of compiler:compile (see MavenProjectConfigCollector) to determine that the helidon-cli-maven-plugin is configured as an extension.

---

Steps to reproduce:

Configure the helidon-cli-maven-plugin like this:

<plugin>
    <groupId>io.helidon.build-tools</groupId>
    <artifactId>helidon-cli-maven-plugin</artifactId>
    <extensions>true</extensions>
    <configuration>
        <devLoop>
            <fullBuild>
                <phase>generate-resources</phase>
            </fullBuild>
        </devLoop>
    </configuration>
</plugin>

Run helidon dev.

---

Possible ways to fix this:

• Update the extension validation logic to be independent of the lifecycle configuration. I.e. simply validate that we can observe build events
• Resolve the executions in the full build life-cycle and assert them instead of hard-coding compiler:compile.