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.

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

dependency-track.updateParent fails if you have set a name on your maven projects #414

Open
Zune01 opened this issue Apr 17, 2024 · 0 comments

Comments

@Zune01
Copy link

Zune01 commented Apr 17, 2024

The option dependency-track.updateParent fails if you (like us) have set the name parameter on all Maven projects to something human-readable.
The problem is that the project in Dependency-Track is created with artifactId as name, so it fails to find all our projects.
However, by changing the line

  @Parameter(defaultValue = "${project.parent.artifactId}", property = "dependency-track.parentName")
  private String parentName;

in UploadBomMojo it works with our projects as well.
Thing is, Maven inserts artifactId into name if it's not set, which explains why it works in all other cases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant