Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] [RULES] False positive on "JBoss deprecated logging annotations" jboss-eap5and6to7-java-09000 #654

Open
1 task done
abrugaro opened this issue Jul 15, 2024 · 2 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Milestone

Comments

@abrugaro
Copy link
Contributor

abrugaro commented Jul 15, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Konveyor version

0.5 beta 1

Priority

Undefined (Default)

Current Behavior

No response

Expected Behavior

No response

How Reproducible

Always (Default)

Steps To Reproduce

No response

Environment

No response

Anything else?

Tested with Kantra b0.5 beta1
Target: eap8 (and others)
Source: none
Source code used: https://github.com/sonatype/nexus-public
Rule triggered: jboss-eap5and6to7-java-09000 JBoss deprecated logging annotations
Report: https://drive.google.com/file/d/1TbdLS4_728DgxbB88F7YcXw84jK2elty/view?usp=drive_link

This rule reported 11 incidents for the application, all of them were related to annotations or other elements on unrelated packages.

image
image
image

@abrugaro abrugaro added kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jul 15, 2024
@konveyor-ci-bot
Copy link

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

@konveyor-ci-bot konveyor-ci-bot bot added the needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. label Jul 15, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in Planning Jul 15, 2024
@dymurray dymurray added this to the v0.5.0 milestone Jul 15, 2024
@dymurray dymurray added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jul 15, 2024
@konveyor-ci-bot konveyor-ci-bot bot removed the needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. label Jul 15, 2024
@dymurray dymurray added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jul 18, 2024
@dymurray dymurray modified the milestones: v0.5.0, v0.5.1 Jul 18, 2024
@dymurray
Copy link
Contributor

dymurray commented Aug 1, 2024

Confirmed I can still reproduce this on 0.5.0. The results are not as many as the reporter but still seeing false positives on this rule.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
Status: 🆕 New
Development

No branches or pull requests

2 participants