-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[BUG] no explicit encoding set error when running rules #787
Comments
This issue is currently awaiting triage. |
Is there any chance that you could attach the analysis logs to the issue, it will narrow the issue down of which provider condition is causing the problem. |
Hi @shawn-hurley I have already paste the |
Oh my! I must be reading too fast! I am sorry! Can you run with Sorry for missing the logs |
Thanks @shawn-hurley , I add the log level, the
I test this rule: - customVariables: []
labels:
- konveyor.io/include=always
links: []
ruleID: 3rd-party-spring-03001
tag:
- Spring Boot Configuration
- Spring Boot Auto-configuration
- Spring Boot Component Scan
when:
java.referenced:
location: ANNOTATION
pattern: org.springframework.boot.autoconfigure.SpringBootApplication |
Is there an existing issue for this?
Konveyor version
0.6.0
Priority
Critical
Current Behavior
Repo: https://github.com/spring-projects/spring-petclinic.git
Rule: 3rd-party-spring-03001
for the app, in windup, the rule can be executed.
When running with kantra, it report error.
Command:
kantra analyze --input ./spring-petclinic --output ./spring.localtest --target azure-container-apps --target cloud-readiness --target linux --overwrite --enable-default-rulesets=false --rule=xxx/01-3rd-party-spring.windup.yaml
analysis.log:
output.yaml:
Is there some thing wrong with java lsp server?
Expected Behavior
the project should add
Spring Boot Configuration
,Spring Boot Auto-configuration
,Spring Boot Component Scan
tags because the rule can be matchedHow Reproducible
Always (Default)
Steps To Reproduce
No response
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: