With devonfw/devon4j#480 a guide with hints on how to migrate a Spring to a Quarkus application is added. Furthermore, it would be very helpful if there were tools that simplify the migration and perform some steps automatically. Red Hat already provides a Migration Toolkit that should help in this topic. With it you can analyze a Spring project and then get hints which dependencies cannot be used for Quarkus and which Quarkus extensions they have to be replaced by. However, nothing is done automatically.
We should evaluate and come up with ideas on how this can be realized. A first start could be to make CobiGen fit for Quarkus, so that CobiGen can create the needed classes, as it is now the case for Spring applications.
With devonfw/devon4j#480 a guide with hints on how to migrate a Spring to a Quarkus application is added. Furthermore, it would be very helpful if there were tools that simplify the migration and perform some steps automatically. Red Hat already provides a Migration Toolkit that should help in this topic. With it you can analyze a Spring project and then get hints which dependencies cannot be used for Quarkus and which Quarkus extensions they have to be replaced by. However, nothing is done automatically.
We should evaluate and come up with ideas on how this can be realized. A first start could be to make CobiGen fit for Quarkus, so that CobiGen can create the needed classes, as it is now the case for Spring applications.