-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reduce the noise in verbose flattened BOMs #3702
Comments
After thinking of it again, I'd say the line numbers are not useful at all. What matters are the versions and the origin BOM. Those are much more stable. |
Yeah I think it would help. Lets try and see how it goes. |
I'll also replace the current project's version literal with something like |
I think we found an acceptable way forward with this. Much less noise generated since 171483b. |
For me it's becoming a source of confusion / merge conflict pain when the line number comments in the verbose BOMs are constantly being shuffled around.
Is there any value in having the verbose BOMs (or even any of the generated BOMs) checked into git?
If not, maybe we output them to a known location in the
target
directory so that they can still be inspected if desired.The text was updated successfully, but these errors were encountered: