Analysis of components in internal repository #3442
Replies: 1 comment
-
It's working now, so closing this. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm hoping for some help on this one:
We have a Nexus repository that which also hold our maven repositories and I tried setting it up for Dependency Track to use, but nothing happens. I'm a bit unsure if the Dependency Track do infact get information, if the setup was correct, but I don't see any access denied, or other things failing, in the log file when the project is scanned.
We would like to get those warning with old versions for our own artifacts / components in projects that is being analyzed. External references URL of our compontens in the Compontent Details points to our nexus maven repository with the type distribution.
I have setup our components as being internal too.
Beta Was this translation helpful? Give feedback.
All reactions