Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a proper maven archetype for Quarkus+Devon #492

Open
matus-m opened this issue Nov 2, 2021 · 1 comment
Open

Create a proper maven archetype for Quarkus+Devon #492

matus-m opened this issue Nov 2, 2021 · 1 comment
Assignees
Labels

Comments

@matus-m
Copy link
Contributor

matus-m commented Nov 2, 2021

At the moment, the guide only links to code.quarkus.io website with some preselected packages as suggestion for creating new project.
We should create a proper maven archetype that:

  • creates a project with recommended extensions(e.g. imperative REST + JPA)
  • follows naming and package conventions of devon
  • has relevant sample code and config
  • maybe also contains k8s/helm

Ideally, we would have multiple variants of the archetype, matching the common scenarios e.g. imperative CRUD app, reactive messaging, reactive CRUD.... but that can be extended in the future

@matus-m matus-m added the enhancement New feature or request label Nov 2, 2021
@matus-m
Copy link
Contributor Author

matus-m commented Nov 9, 2021

The first and easiest archetype to start with could be a simple imperative CRUD backend with REST API, with suggested extension list:

  • resteasy-jackson
  • hibernate-orm/spring-data-jpa
  • opentelemetry
  • micrometer-metrics/prometheus
  • logging-json
  • fault-tolerance
  • smallrye-openapi
  • jdbc-postgresql

@EduardKrieger EduardKrieger self-assigned this Dec 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants