Hi Jeremy,
On 30.04.2025 18:26, Jeremy Landis wrote:
Because on a physical release, the deploy plugin is taken over by the central publishing
extension and cyclonedx relies on deploy, this flag was necessary
`<skipNotDeployed>false</skipNotDeployed>` for cyclonedx to deploy during
release.
The CycloneDX Maven Plugin is not the only one that will incorrectly
detect, which artifacts are deployed. I copied the deployment detection
code from Maven Artifact Plugin:
https://github.com/apache/maven-artifact-plugin/blob/master/src/main/java/org/apache/maven/plugins/artifact/buildinfo/PluginUtil.java
That code is clearly a hack, but as far as I know, there is no better
alternative right now. Maybe something could be introduced in the Maven
4 model.
Piotr
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
