The POM that is generated during Maven deployment refers to the org.jenkins-ci.plugins:plugin parent POM using the coreVersion from the jenkinsPlugin configuration.

However, from Jenkins 1.646 onwards, the plugin parent POM is no longer a part of the Jenkins Core, so the generated POM will refer a non-existing version.

This inconsistency makes it difficult to consume the API of the built plugin from another plugin, since the artifact will not resolve properly.

See the Plugin tutorial for advice on how to specify the core version when using a more recent parent POM.

I don't know how to sensibly select the parent POM automatically. Perhaps the latest available version should be the default, with optional configuration to specify it explicitly?