Skip to content

Conversation

@GuusLieben
Copy link
Member

Type of Change

  • Chore (changes to the build process or auxiliary tools)
  • Feature (non-breaking change that adds functionality)

Description

Minor side quest, to introduce automated scaffolding of new (internal) modules, as over time the complexity of adding new modules has increased.

This includes:

  • Creating a new Maven project with the appropriate groupId, artifactId, and version.
  • Setting up the basic directory structure for:
    • Source code and resources
    • Test code and resources
    • Antora documentation
  • Registers the new module in the assembly POM
  • Registers the new module in the documentation indexes (local and release)
  • Reminding of required manual steps (which cannot be automated due to ordering/formatting conventions)

How the Changes Have Been Tested

Generated various modules locally to verify correct behavior, both with and without documentation setup.

Checklist

  • I have performed a self-review of my own code
  • I have added documentation that describes my changes
  • Any dependent changes have been merged and published in downstream modules
  • I have rebased my branch on top of the latest develop branch

@GuusLieben GuusLieben added this to the 0.7.0 milestone Jan 17, 2026
@GuusLieben GuusLieben self-assigned this Jan 17, 2026
@GuusLieben GuusLieben merged commit abc6a7b into develop/0.7.0 Jan 17, 2026
9 checks passed
@GuusLieben GuusLieben deleted the feature/module-archetype branch January 17, 2026 10:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant