Feature: Teach plugin to handle central-publishing-maven-plugin extension as deployment type

[hazendaz]

In June, legacy maven central deployments will be blocked. All users are being told to follow instructions here https://central.sonatype.org/publish/publish-portal-maven/ to switch over.

Presumably most would follow pattern of testing snapshot first which is documented as using the deploy plugin so cyclonedx would execute. However, I don't think anyone would or should be aware that suddenly this plugin will fail to execute upon release. While those checking closely like I did will notice this, they would have already spent the release and probably don't wish to do it over.

It would be nice if this plugin could learn the new publishing plugin being used to avoid the issue. As a fall back, I think it needs to be documented more up front that 'skipNotDeployed' will need added to turn that back on.

[apupier]

The message (which is not failing the build) is:

[INFO] --- cyclonedx:2.9.1:makeAggregateBom (default) @ XXXX ---
[INFO] Skipping CycloneDX goal, because module skips deploy

To ensure the SBom is generated, as mentioned in first message, the current workaround is to set the in configuration skipNotDeployed to false, so it will give something like:

<plugin>
        <groupId>org.cyclonedx</groupId>
	<artifactId>cyclonedx-maven-plugin</artifactId>
	<version>2.9.1</version>
	<executions>
		<execution>
			<phase>package</phase>
			<goals>
				<goal>makeAggregateBom</goal>
			</goals>
			<configuration>
			        <!-- to be removed when https://github.com/CycloneDX/cyclonedx-maven-plugin/issues/597 is fixed-->
				<skipNotDeployed>false</skipNotDeployed>
			</configuration>
		</execution>
	</executions>
</plugin>

[hohwille]

See m-m-m/mmm#2 - maybe the linked wiki page could be of interest.
In case you also have experience to share it is great if users can collaborate.