Spotbugs error in module 1 qmoney

[Akanksha_Dadhich]

i am getting this error while running gradle build how to resolve this spotbug

Task :qmoney:spotbugsMain FAILED

FAILURE: Build failed with an exception.

• What went wrong:
  Execution failed for task ‘:qmoney:spotbugsMain’.

SpotBugs rule violations were found. See the report at: file:///home/crio-user/workspace/akankshadadhich3001-ME_QMONEY/qmoney/build/reports/spotbugs/main.html

• Try:
  Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

• Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0.
Use ‘–warning-mode all’ to show the individual deprecation warnings.
See https://docs.gradle.org/5.2.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 4s
13 actionable tasks: 1 executed, 12 up-to-date

[Akanksha_Dadhich]

i ran --debg but i am not understanding it

14:59:08.743 [DEBUG] [org.gradle.internal.resources.AbstractTrackedResourceLock] Daemon worker Thread 6: released lock on root.1.7
14:59:08.743 [DEBUG] [org.gradle.execution.plan.DefaultPlanExecutor] Execution worker [Thread[Daemon worker Thread 6,5,main]] finished, busy: 4.14 secs, idle: 0.145 secs
14:59:08.743 [DEBUG] [org.gradle.execution.plan.DefaultPlanExecutor] Execution worker [Thread[Execution worker for ‘:’,5,main]] finished, busy: 0.0 secs, idle: 4.285 secs
14:59:08.743 [DEBUG] [org.gradle.execution.taskgraph.DefaultTaskExecutionGraph] Timing: Executing the DAG took 4.286 secs
14:59:08.744 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationExecutor] Completing Build operation ‘Run tasks’
14:59:08.744 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationExecutor] Build operation ‘Run tasks’ completed
14:59:08.744 [DEBUG] [org.gradle.internal.work.DefaultWorkerLeaseService] Worker lease root.1 completed (0 worker(s) in use)
14:59:08.744 [DEBUG] [org.gradle.internal.resources.AbstractTrackedResourceLock] Daemon worker Thread 6: released lock on root.1
14:59:08.744 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
14:59:08.744 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] FAILURE: Build failed with an exception.
14:59:08.744 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
14:59:08.744 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * What went wrong:
14:59:08.744 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] Execution failed for task ‘:qmoney:spotbugsMain’.
14:59:08.744 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] > SpotBugs rule violations were found. See the report at: file:///home/crio-user/workspace/akankshadadhich3001-ME_QMONEY/qmoney/build/reports/spotbugs/main.html
14:59:08.744 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
14:59:08.744 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * Try:
14:59:08.745 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] Run with --stacktrace option to get the stack trace. Run with --scan to get full insights.
14:59:08.745 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
14:59:08.745 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * Get more help at https://help.gradle.org
14:59:08.745 [WARN] [org.gradle.internal.featurelifecycle.LoggingDeprecatedFeatureHandler]
Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0.
Use ‘–warning-mode all’ to show the individual deprecation warnings.
See https://docs.gradle.org/5.2.1/userguide/command_line_interface.html#sec:command_line_warnings
14:59:08.745 [ERROR] [org.gradle.internal.buildevents.BuildResultLogger]
14:59:08.745 [ERROR] [org.gradle.internal.buildevents.BuildResultLogger] BUILD FAILED in 4s
14:59:08.745 [LIFECYCLE] [org.gradle.internal.buildevents.TaskExecutionStatisticsReporter] 13 actionable tasks: 1 executed, 12 up-to-date
14:59:08.745 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationExecutor] Completing Build operation ‘Run build’
14:59:08.745 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationExecutor] Build operation ‘Run build’ completed
14:59:08.746 [DEBUG] [org.gradle.process.internal.health.memory.MemoryManager] Emitting OS memory status event {Total: 32655380480, Free: 22656380928}
14:59:08.746 [DEBUG] [org.gradle.launcher.daemon.server.health.LowMemoryDaemonExpirationStrategy] Received memory status update: {Total: 32655380480, Free: 22656380928}
14:59:08.746 [DEBUG] [org.gradle.process.internal.health.memory.MemoryManager] Emitting JVM memory status event {Maximum: 477626368, Committed: 285736960}
14:59:08.773 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for file content cache (/home/cri
o-user/workspace/akankshadadhich3001-ME_QMONEY/.gradle/5.2.1/fileContent)

[sashi_Crio.Do]

Please refer to the following FAQ

How to fix SpotBugs efficiently

[Artboard Copy 4] SpotBugs is a program which uses static analysis to look for bugs in Java code. It is free software, distributed under the terms of the GNU Lesser General Public License. SpotBugs can analyze programs compiled for any version of Java, from 1.0 to 1.9. SpotBugs generate an HTML file, describing the issues which are present in your application and provides required solutions on what has to be improved. SpotBugs are generated after gradlew build command is executed. When grad…

[Suyash]

@Akanksha_Dadhich

SpotBugs rule violations were found. See the report at: file:///home/crio-user/workspace/akankshadadhich3001-ME_QMONEY/qmoney/build/reports/spotbugs/main.html

Hey @Akanksha_Dadhich
Just do control+click on the report link .
It will open you an html file which you can view on your browser and remove the errors.

[Akanksha_Dadhich]

i did not being able to understand these errors

[Akanksha_Dadhich]

showing this error

[Suyash]

Hey @Akanksha_Dadhich ,do google the error.
Read and understand what is the error and why is it generated.
Search for how you can overcome with your current method.

[NishanthR]

Hey @Akanksha_Dadhich. You have to specify an encoding format while getting the string contents from the byte-array, you need to set an encoding format as good programming practice. Do look up on Details title in your report for more.