You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have quite a lot of internal dependencies in our projects where we have a zip file as artifact (using @zip as extension in the dependencies block in build.gradle).
Using this plugin, this dependencies are correctly included in the bom file with ?type=zip.
Also in dependency-track, they are correctly shown in the Components tab.
However, when using Show in dependency graph in dependency-track, the root of the graph is shown with Dependency could not be found in dependency graph displayed above.
I had a quick look through the generation of the graph in the code and found that here and here the dependencies and child dependencies are only added to the graph if the type is either jar or aar.
To get a more complete graph I would propose to also add dependencies of other types to the dependency-graph.
The text was updated successfully, but these errors were encountered:
zkstchhh
added a commit
to zkstchhh/cyclonedx-gradle-plugin
that referenced
this issue
Mar 27, 2024
We have quite a lot of internal dependencies in our projects where we have a zip file as artifact (using
@zip
as extension in the dependencies block in build.gradle).Using this plugin, this dependencies are correctly included in the bom file with
?type=zip
.Also in dependency-track, they are correctly shown in the
Components
tab.However, when using
Show in dependency graph
in dependency-track, the root of the graph is shown withDependency could not be found in dependency graph
displayed above.I had a quick look through the generation of the graph in the code and found that here and here the dependencies and child dependencies are only added to the graph if the type is either
jar
oraar
.To get a more complete graph I would propose to also add dependencies of other types to the dependency-graph.
The text was updated successfully, but these errors were encountered: