Skip to content

MLE-30952 Deleting pom.xml#1956

Merged
jonmille merged 1 commit into
developfrom
MLE-30952
Jul 7, 2026
Merged

MLE-30952 Deleting pom.xml#1956
jonmille merged 1 commit into
developfrom
MLE-30952

Conversation

@jonmille

@jonmille jonmille commented Jul 7, 2026

Copy link
Copy Markdown

Deleting pom.xml so that Black Duck does not scan it.

Deleting pom.xml so that Black Duck does not scan it
@jonmille jonmille requested a review from rjdew-progress July 7, 2026 14:13
Copilot AI review requested due to automatic review settings July 7, 2026 14:13

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR removes the repository’s root pom.xml (previously generated via Gradle) with the intent of preventing Black Duck from scanning it.

Changes:

  • Deleted the root pom.xml file from the repository.
Comments suppressed due to low confidence (1)

pom.xml:1

  • Deleting this generated pom.xml removes the Maven manifest GitHub can use for Dependency Graph/Dependabot-style visibility (the POM header notes it was generated for GitHub’s Dependency Graph feature). If the goal is to stop Black Duck from scanning this file, consider keeping the generated POM and excluding it via Black Duck/Synopsys Detect configuration instead (or switch to GitHub’s Gradle dependency submission) so dependency/vulnerability reporting isn’t reduced.

@jonmille jonmille merged commit 3636af6 into develop Jul 7, 2026
4 of 5 checks passed
@jonmille jonmille deleted the MLE-30952 branch July 7, 2026 14:23
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

Successfully merging this pull request may close these issues.

3 participants