Migration-Guide-1.11

This Jira will propose how MTA can cater for the changes described in the Migration guide. After those proposals have been validated then separate Jira tasks can be generated to for each change described in the guide.

The target will be quarkus1 .
So to migrate from quarkus 1.10 to quarkus 1.11 the rules use
sourceTechnology id="quarkus1" versionRange="(,10]"
targetTechnology id="quarkus1" versionRange="[11,)"

Use the create-test-jar.sh script
to create the jar file to be used in the tests for all of the rules except the Log min level rule.
Instructions
create an empty folder
copy the create-test-jar.sh script inside
execute $ ./create-test-jar.sh io/quarkus/jackson
it'll create a test.jar file in the same folder, in this case it will have the directory structure io/quarkus/jackson that was supplied as a parameter to the script.
Obviously that will vary in each rule and contain the path of the dependency being searched for.

Log min level
I would suggest that we could have a rule that searches the application.properties for the ".level=DEBUG"
If so generate the message transcribed from the guide with a link to the guide and a link to https://quarkus.io/guides/logging

Non application endpoints moved to /q/ namespace
No rule required.

Jackson
I would suggest having a rule that looks for the io.quarkus:quarkus-resteasy-jackson dependency in the POM when in source mode
Or the directory path (shaded jar).
If discovered generated an potential issue. The text and the link can be taken directly from the migration guide.

Kubernetes
I would suggest having a rule that looks for the io.quarkus:quarkus-kubernetes dependency in the POM when in source mode
Or directory path (shaded jar).
If discovered generated an potential issue. Kubernetes Client has been upgraded to version 5.
Please refer to the Kubernetes Client migration guide for more information.

Hibernate Search ORM + Elasticsearch
Look for the io.quarkus:quarkus-hibernate-search-orm-elasticsearch dependency in the POM when in source mode
or the directory path (shaded jar).
Potential issue
Add the text and links in the guide plus https://quarkus.io/guides/hibernate-search-orm-elasticsearch

MongoDB Panache
I would suggest having a rule that looks for the io.quarkus:quarkus-mongo-panache dependency in the POM when in source mode
Or the directory path (shaded jar).
If discovered generated an potential issue. The text and the link can be taken directly from the migration guide.
Also add the link to https://quarkus.io/guides/mongodb-panache

GraalVM 20.3
No rule required.