add isDeployable()

[hboutemy]

New feature, improvement proposal

utility to detect if a Maven module is installed deployed or not, to be able to change a plugin goal's behaviour if the module being built is just a transient reactor-level only module, or a module that really deploy to remote repository of r future external

to consolidate what is done:

• in https://github.com/apache/maven-artifact-plugin/blob/master/src/main/java/org/apache/maven/plugins/artifact/buildinfo/PluginUtil.java
• and https://github.com/CycloneDX/cyclonedx-maven-plugin/blob/master/src/main/java/org/cyclonedx/maven/BaseCycloneDxMojo.java#L603

with current addition of a new case CycloneDX/cyclonedx-maven-plugin#604

why in maven-archiver?

This is not really an archiving feature. Putting this code here is just because it's another case where we analyze plugin configuration to detect facts on the build process, like we do in https://github.com/apache/maven-archiver/blob/master/src/main/java/org/apache/maven/shared/archiver/BuildHelper.java around maven-compiler-plugin

[hboutemy]

1. diving into maven-artifact-plugin case = support central-publishing-maven-plugin for detectSkip maven-artifact-plugin#173

in this plugin, the new central-publishing-maven-plugin is not causing strong issue: maven-artifact-plugin continues to work quite normally in project that migrated to it, the only edge case that has to be improved is when a project adds configuration to NOT deploy some modules (in multi-module builds)

2. on the cyclonedx-maven-plugin case = skip logic in the plugin is broken CycloneDX/cyclonedx-maven-plugin#605 / Handle central-publishing-maven-plugin for skipNotDeployed detection CycloneDX/cyclonedx-maven-plugin#604

it seems the detection algorithm is fully different, as it looks like projects using central-publishing-maven-plugin are getting everything skipped

I did not yet investigate cyclonedx-maven-plugin fully, as I had my priority on maven-artifact-plugin
but it seems the consequences of central-publishing-maven-plugin are completely different

consequence here: we're not ready for consolidating the algorithm from m-artifact-p and cyclonedx-m-p into maven-archiver: post-poning the idea