Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Using pom groupId leading to bad CPEs for plugins, leading to false positives #395

Closed
luhring opened this issue Apr 19, 2021 · 0 comments · Fixed by #399
Closed

Using pom groupId leading to bad CPEs for plugins, leading to false positives #395

luhring opened this issue Apr 19, 2021 · 0 comments · Fixed by #399
Assignees
@luhring
Labels
bug Something isn't working

Comments

@luhring
Copy link
Contributor

luhring commented Apr 19, 2021

This is specific to Java packages...

E.g.

  1. Plugins with groupId: com.atlassian.jira.plugins — matches Jira itself
  2. Plugins with groupId: com.cloudbees.jenkins.plugins — matches Jenkins itself
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@luhring luhring

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Don't use pom groupId for Jenkins and Jira plugins anchore/syft
1 participant
@luhring