You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
We upgrade to release 6.3 and we got error java.lang.ClassNotFoundException: edu.umd.cs.findbugs.LaunchAppropriateUI from spotbugs. It looks this commit causes the issue.
We are able to reproduce it with a minimal configuration.
$bazel run //:spotbugs_bin
pip_login: login credential still valid: To force a token refresh, use the -f flag
Regenerating ~/.m2/settings.xml
Regenerating ~/.gradle/gradle.properties
maven_login ok
WARNING: Running Bazel server needs to be killed, because the startup options are different.
Starting local Bazel server and connecting to it...
INFO: Invocation ID: 821b3105-bbd9-4324-97df-98f2ec5823e9
INFO: Analyzed target //:spotbugs_bin (128 packages loaded, 1030 targets configured).
INFO: Found 1 target...
Target //:spotbugs_bin up-to-date:
bazel-bin/spotbugs_bin
bazel-bin/spotbugs_bin.jar
INFO: Elapsed time: 10.802s, Critical Path: 4.23s
INFO: 65 processes: 2 disk cache hit, 7 internal, 52 darwin-sandbox, 4 worker.
INFO: Build completed successfully, 65 total actions
INFO: Running command line: bazel-bin/spotbugs_bin
Error: Could not find or load main class edu.umd.cs.findbugs.LaunchAppropriateUI
Caused by: java.lang.ClassNotFoundException: edu.umd.cs.findbugs.LaunchAppropriateUI
I found that the rules_jvm_external release 6.3 adds feature to support pom. After we upgrade and run bazel run @unpinned_maven//:pin, it removed the com.github.spotbugs:spotbugs from the packages section of maven_install.json.
edu.umd.cs.findbugs.LaunchAppropriateUI should in edu.umd.cs.findbugs.launchGUI. Can you help to take a look why package com.github.spotbugs:spotbugs got removed?
Description:
We upgrade to release 6.3 and we got error
java.lang.ClassNotFoundException: edu.umd.cs.findbugs.LaunchAppropriateUI
from spotbugs. It looks this commit causes the issue.We are able to reproduce it with a minimal configuration.
rules_jvm_external version: 6.3
rules_jvm version: 0.24.0
WORKSPACE.bazel
BUILD.bazel
I found that the rules_jvm_external release 6.3 adds feature to support pom. After we upgrade and run
bazel run @unpinned_maven//:pin
, it removed thecom.github.spotbugs:spotbugs
from thepackages
section of maven_install.json.edu.umd.cs.findbugs.LaunchAppropriateUI
should inedu.umd.cs.findbugs.launchGUI
. Can you help to take a look why packagecom.github.spotbugs:spotbugs
got removed?package info in maven_install.json before upgrade
The text was updated successfully, but these errors were encountered: