fix(deps): update dependency org.apache.bcel:bcel to v6.7.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
org.apache.bcel:bcel (source)	6.6.1 -> 6.7.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[ThrawnCA]

Looks like our build isn't ready for the newer BCEL.

[hazendaz]

Adding link to the change log for bcel for easy reference while looking into this https://commons.apache.org/proper/commons-bcel/changes-report.html#a6.7.0.

[gtoison]

@hazendaz it seems to me that the issue is that we build with BCEL 6.7.0 and then we analyze the project with the SpotBugs Gradle plugin (which was built with the previous version of BCEL) but the plugin uses BCEL 6.7.0, not the version it was built with.
Does it make sense?

[teicher]

Since bcel-6.5.0 has CVE-2022-42920 (CRITICAL)
the current spotbugs release 4.7.3 is reported as causing vulnerabilities in dependency-check...

[JuditKnoll]

Since bcel-6.5.0 has CVE-2022-42920 (CRITICAL) the current spotbugs release 4.7.3 is reported as causing vulnerabilities in dependency-check...

As far as I can see, the current master is on bcel version 6.6.1, which is not affected by this problem. However, it would be great to have this PR in spotbugs 4.7.4, it is not critical.

[nbauma109]

Several issues here, I noticed at least 2:

• Constant pool does not allow index 0 anymore, getConstant at index 0 now throws exception apache/commons-bcel@77c7997
• A regression due to a fix I did for BCELifier Code coverage and bug fixes for bcelifier apache/commons-bcel#171 that I will fix soon

[JuditKnoll]

The relevant PR (apache/commons-bcel#221) got merged to bcel, so the next bcel version should work with the changes in this PR. However, I don't have any timeline info about the bcel release.

[hazendaz]

letting renovate rebase again to see if docs is related to us or that process since all recent PRs are failing today.

[hazendaz]

arggg...mistakenly messed this up. Will fix it...