Migrate project command in Quarkus tooling #9875
Labels
area/devtools
Issues/PR related to maven, gradle, platform and cli tooling/plugins
kind/enhancement
New feature or request
Comments
ia3andy
added
the
area/devtools
ia3andy
added a commit
to ia3andy/quarkus
that referenced
this issue
Jun 9, 2020
This is part of quarkusio#8178 - Improved packages names and content - Improved general readability and consistency - Added ExtensionManager to define a high level way of managing (read/write) extensions in any QuarkusProject - Removed most unsafe Gradle operations which were outside of the Gradle plugin (we need to figure out a way to improve the "generic" gradle support to make it compatible again..) - Removed existing project support with the create command (throws an error) -> quarkusio#9875 - Removed compatibility with project without the Quarkus platform bom defined - Remove SetupIT which mostly duplicate CreateProjectMojoIT
ia3andy
added a commit
to ia3andy/quarkus
that referenced
this issue
Jun 9, 2020
This is part of quarkusio#8178 - Improved packages names and content - Improved general readability and consistency - Added ExtensionManager to define a high level way of managing (read/write) extensions in any QuarkusProject - Removed most unsafe Gradle operations which were outside of the Gradle plugin (we need to figure out a way to improve the "generic" gradle support to make it compatible again..) - Removed existing project support with the create command (throws an error) -> quarkusio#9875 - Removed compatibility with project without the Quarkus platform bom defined - Remove SetupIT which mostly duplicate CreateProjectMojoIT
ia3andy
added a commit
to ia3andy/quarkus
that referenced
this issue
Jun 10, 2020
This is part of quarkusio#8178 - Improved packages names and content - Improved general readability and consistency - Added ExtensionManager to define a high level way of managing (read/write) extensions in any QuarkusProject - Removed most unsafe Gradle operations which were outside of the Gradle plugin (we need to figure out a way to improve the "generic" gradle support to make it compatible again..) - Removed existing project support with the create command (throws an error) -> quarkusio#9875 - Removed compatibility with project without the Quarkus platform bom defined - Remove SetupIT which mostly duplicate CreateProjectMojoIT
johnaohara
pushed a commit
to johnaohara/quarkus
that referenced
this issue
Jun 29, 2020
This is part of quarkusio#8178 - Improved packages names and content - Improved general readability and consistency - Added ExtensionManager to define a high level way of managing (read/write) extensions in any QuarkusProject - Removed most unsafe Gradle operations which were outside of the Gradle plugin (we need to figure out a way to improve the "generic" gradle support to make it compatible again..) - Removed existing project support with the create command (throws an error) -> quarkusio#9875 - Removed compatibility with project without the Quarkus platform bom defined - Remove SetupIT which mostly duplicate CreateProjectMojoIT
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Most users didn't know about that feature, but it was possible to migrate existing projects to Quarkus with the create command (before #9787).
To put ourselves in a greenfield situation and make it possible to have as much stability as possible in our CodeStarts (#8134), I removed that feature from the create.
The idea would be to separate that feature and add a new command "migrate" allowing to convert an existing project to Quarkus (it could be in experimental mode for a while since it's hard to be really consistant for this)
The text was updated successfully, but these errors were encountered: