Implement first rev of quarkus:update

[emmanuelbernard]

Description

quarkus:update aims to help user migrate from one version of Quarkus to the other as seamlessly as possible. An example of this is the Angular ng update command. Since Quarkus updates frequently compared to the usual Java framework, the goal of this command is to make the update as smooth and short as possible.

Implementation ideas

We need to start small and concrete. There are about a million grandiose possible ideas but let's build a base that helps people concretely and improve over time.

Here is a proposal for the minimal viable solution:

• detect the list of extensions used concretely by the project
• list extensions used that are no longer present in the platform (that were before)
• list extensions used that were marked as compatible with the old Quarkus core but are no longer
• list dependencies that overrides the platform BOM versions recommended
• list the new version of GraalVM to use for native compilation
• list and display (or URL) the migration guides for each extension used by the project if there is a necessary change
  • explicit API usage update
  • dependency update (and a pointer to their migration guide? Wrapped?)
• update the BOM version(s)

Note: this does not apply to extension development but to end user project at this stage.

Necessary base work

Any change to an extension code (Pull Request) must declare whether or not the change does break things. And if it does, it must offer a .adoc representing the necessary migration steps (or lack of). This means, we need to

• define a metadata structure representing the migration guides for a given extension between two versions
• build migration guides documents with permanent URLs (per extension, per version)

Further more grandiose ideas (for later)

• propose or apply configuration file changes upon updates
• detect via sig comparison of a possible breaking change at extension PR time
• detect via sig comparison of a possible breaking change on the project

[johnaohara]

This could also be useful in quarkus:update https://github.com/quarkusio/quarkus/issues/9149

[maxandersen]

• list the new version of GraalVM to use for native compilation

Is this information even available anywhere in an artifact today ? @aloubyansky @gsmet ?

list and display (or URL) the migration guides for each extension used by the project if there is a necessary change

• explicit API usage update
• dependency update (and a pointer to their migration guide? Wrapped?)

I would not include this as part of MVP of this feature as doc info, migration guide, api usage etc. are not. in any form available/defined today. @emmanuelbernard

[emmanuelbernard]

list and display (or URL) the migration guides for each extension used by the project if there is a necessary change

• explicit API usage update
• dependency update (and a pointer to their migration guide? Wrapped?)

I would not include this as part of MVP of this feature as doc info, migration guide, api usage etc. are not. in any form available/defined today. @emmanuelbernard

My hope was that this work would trigger the definition of a metadata format and could be empty for extensions that need to catch up. But yes can definitely be LessMVP

[geoand]

@gsmet @maxandersen I assume we can close this as quarkus update pretty much fits the bill, correct?