Add className and path parameters in CLI
See original GitHub issueEDIT:
See comment https://github.com/quarkusio/quarkus/issues/14437#issuecomment-1067739526
Legacy:
They are already definable as codestart data: https://github.com/quarkusio/quarkus/blob/master/independent-projects/tools/devtools-common/src/main/java/io/quarkus/devtools/codestarts/quarkus/QuarkusCodestartData.java#L32-L39
We need to plug them to distinct parameters (resteasy.class-name
, resteasy-reactive.class-name
, …) instead of a generic one in the CreateProjectMojo
and the io.quarkus.cli.Create
:
https://github.com/quarkusio/quarkus/blob/main/independent-projects/tools/devtools-common/src/main/java/io/quarkus/devtools/codestarts/quarkus/QuarkusCodestartData.java#L39-L46
This issue also includes updating the guides to use those new parameters.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (4 by maintainers)
@cristian-com I think we should wait for the new CLI before doing that one. Let me find you something 😃
To give a bit of context, the problem is that when selecting multiple codestarts (i.e: resteasy + spring-web, …) then
path
andclassName
parameters are ambiguous. The current behavior is to ignore them in that case.With a bit more feedback on how codestarts are used, it seems that beside the basics (groupId, extensions…) customizing the generated code is not a strong need and would be complex to maintain and document with that many extensions. Still we have some “main” extensions resteasy, resteasy-reactive, spring-web and maybe some other in the future for which it is nice to configure the
className
and thepath
.So, in the end, I believe we should:
className
and thepath
in the Maven pluginclassName
and thepath
in the Quarkus CLI.FYI:
org.acme
is the default