Fix an issue where the published module doesn't contain a 'cpp' type.
Stop using 'buildinfo.BuildPublishCommand' for publishing build-info, instead - create the build-info and publish using jfrog-client-go's Artifactory Service Manager.
This problem originates in the way that 'buildinfo.BuildPublishCommand' executes the publishing process:
UploadCommand deploys artifacts to Artifactory, and saves the produced build-info to the file-system as 'partial' - this is an operation made by jfrog-cli-core which we cannot change.
The yocto-plugin generated a build-info, populated by the build's dependencies, and saved it to the file-system as well - with the 'cpp' module type.
'buildinfo.BuildPublishCommand' first reads the partials file, and then appends the saved build-info to it. This way, the module type 'cpp' isn't read into the newly generated build-info of the command, causing an empty type to be published.
Fix an issue where the published module doesn't contain a 'cpp' type. Stop using 'buildinfo.BuildPublishCommand' for publishing build-info, instead - create the build-info and publish using jfrog-client-go's Artifactory Service Manager.
This problem originates in the way that 'buildinfo.BuildPublishCommand' executes the publishing process: