hboutemy commented on issue #304: URL: https://github.com/apache/maven-archiver/issues/304#issuecomment-3349566715
1. diving into maven-artifact-plugin case = https://github.com/apache/maven-artifact-plugin/issues/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 = https://github.com/CycloneDX/cyclonedx-maven-plugin/issues/605 / https://github.com/CycloneDX/cyclonedx-maven-plugin/issues/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](https://central.sonatype.com/artifact/org.sonatype.central/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 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
