Handle central-publishing-maven-plugin for skipNotDeployed detection

[apupier]

this is the plugin replacing nexus-maven-plugin.
The goal used by this plugin is publish and not deploy as other ones

we can notice on the output that it is publish, for instance from https://central.sonatype.org/publish/publish-portal-maven/#publishing

[INFO] --- central-publishing-maven-plugin:0.7.0:publish (injected-central-publishing) @ example ---

fix #597

---

Edit: this is about skipNotDeployed detection #416 / #435
central-publishing-maven-plugin configures all POMs as "maven-deploy-plugin skip" to replace the deployment mechanism: cyclonedx-maven-plugin needs to detect the use of central-publishing-maven-plugin to adapt its "skip" detection approach

[apupier]

I think it will be worthy to add a test. (not understood well how to write a good integration test here yet).
EDIT: one test added for the main test case

i'm also wondering if we should increase the plugin number to 2.30.0 as this is a new feature.

[ppkarwasz]

Looks great! 💯

Could you also add two tests to src/it/makeAggregateBom/skipped?

[apupier]

Could you also add two tests to src/it/makeAggregateBom/skipped?

I added the two tests when skipping

[ppkarwasz]

LGTM!

[ppkarwasz]

@hboutemy,

This PR will solve the immediate problem of projects that use the central-publishing-maven-plugin, where by default the generation of the CycloneDX SBOM is skipped. Could you take a look at this?

Since deployment plugins start appearing like mushrooms after a rain, in the long term we need a different strategy to deal with this.

[apupier]

Any chances to have it reviewed?

The service and so old plugin will be decommissioned in a week https://central.sonatype.org/news/20250326_ossrh_sunset/ , I suspect that potentially a lot of users will hit this issue

[stevespringett]

org.cyclonedx has been migrated to the Central Portal.

[apupier]

org.cyclonedx has been migrated to the Central Portal.

@stevespringett Can you clarify the exact link with the reported issue please?

[hboutemy]

I'll have to rephrase the title of this PR, as it is confusing: Steve reads it as "cyclonedx-maven-plugin already uses central-publishing-maven-plugin to publish to Maven Central"
but the intent of this PR is "support central-publishing-maven-plugin for skipNotDeployed" like what happens to other plugins doing skip detection apache/maven-artifact-plugin#173 (in that case, the parameter is called detectSkip but same logic)

I should have more time in future weeks to work on cyclonedx-maven-plugin: thanks for the work and patience