Skip to content

Define maven archetypes for most typical Vaadin project skeletons. #9004

Description

@TatuLund

Describe your motivation

In the age of AI agentic development there should be a quick method to start the project, preferably from command line. One convenient way to do this is maven archetype. We used to have these for Vaadin 8. My experience with agents is that if they try to build pom.xml from the scratch, they tend to fail often, or iterate very long.

I have tried small AI agentic experiments with Vaadin 8 archetype explicitly stating that in specs, and that works very well.

Archetypes allow easy start using any specific Vaadin version.

Describe the solution you'd like

Set of archetypes for most typical project scenarios

  • Simple single module add-on project / demo in test scope
  • Multimodule add-on project with separate demo module
  • Single module Spring Boot application project
  • Multi-module Spring Boot application project
  • Single module application project without Spring
  • Multi-module application project without Spring

Consider adding more archetypes based on demand

Publish use archetype skill / MCP so that AI will likely use archetype approach automatically.

Describe alternatives you've considered

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions