Plugin dogfooding

[mfoo]

I previously had the following in pom.xml:

<plugin>
    <groupId>${project.groupId}</groupId>
    <artifactId>${project.artifactId}</artifactId>
    <version>${project.version}</version>
    <executions>
        <execution>
            <id>libyear-report</id>
            <goals>
                <goal>analyze</goal>
            </goals>
            <phase>install</phase>
        </execution>
    </executions>
</plugin>

The idea was to execute the current version of the plugin when running mvn install (perhaps it should be verify, and perhaps this is the solution). This caused problems when building the project on a new machine (but somehow not on CI) where the project didn't exist and so couldn't be executed.

I've temporarily removed this execution from the POM, and this ticket is to look at reintroducing it.

[cstamas]

Given resolver distinguishes "existing" (as in, "available from some repository [local or remote]") and "non existing" (as in, "the current POM that may or may not have been built/installed), you need to handle this with care.

Toolbox due this introduces two Mojos: maveniverse/toolbox#37