Skip to content

chore: remove misleading repo artifacts - #196

Closed
thaitraninnovar wants to merge 1 commit into
bridgelink_developmentfrom
feature/remove-misleading-artifacts
Closed

thaitraninnovar wants to merge 1 commit into
bridgelink_developmentfrom
feature/remove-misleading-artifacts

Conversation

@thaitraninnovar

Copy link
Copy Markdown

Summary

  • Remove dependency-check.xml — points at dependency-check-ant.jar, which does not exist in the repo, so the target fails immediately if run. No build file invokes it. We currently have no working dependency scan.
  • Remove custom-extensions/oidc-plugin stub — a bare plugin.xml with zero Java sources and a build.xml deleted back in April. Its presence in the public repo implies a free OIDC plugin exists, which conflicts with OIDC being a licensed capability shipped from BridgeLink-Commercial-Plugins.

Test plan

  • Confirmed no other file references dependency-check.xml or the deleted jar path (git grep -l 'dependency-check' returned only the removed file)
  • Confirmed oidc-plugin had no Java sources and was not referenced by any build file

Remove dependency-check.xml, which points at a jar that does not exist
in the repo and cannot run, and the empty oidc-plugin stub, which
implies a free OIDC capability that is only shipped from the
commercial plugins repo.
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.

1 participant