What did you have in mind?

Currently, the archetypes in this project are created for Java 17,
it might a good idea to allow the user to specify Java 11+.

Are you trying to fix a problem?

No response

Any lead on how this feature can be implemented?

No response

What happened?

The developer id is used for constructing the user profile link, if it contains spaces, it will break.
The current regex matching is not verifying that.

Please provide runtime information.

Not relevant

Relevant log output

No response

How can this issue be reproduced?

No response

What happened?

The owner name should wrapped in " when generating the command.

Please provide runtime information.

Not relevant.

Relevant log output

No response

How can this issue be reproduced?

No response

What did you have in mind?

I'm thinking of making the pop-up menu more engaging and user-friendly.

Are you trying to fix a problem?

Enhancing already available pop-up menu.

Any lead on how this feature can be implemented?

This can be implemented by using CSS.

What did you have in mind?

Adding a couple of basic GitHub workflows, or at least one for pull requests/push.
Perhaps this might not suit the Playground archetypes variants,
but it might be a good idea for the Advanced and Full ones.

Are you trying to fix a problem?

No response

Any lead on how this feature can be implemented?

No response

What did you have in mind?

The current command generator probably represents the peak of my frontend-related expertise.

If you think you can do a better job than me,
you are probably right and your contribution will be very much appreciated. 🤝

The generator-related sources are:

• docs/generator.md is the HTML source, saved as markdown for use with mkdocs.
• docs/generator.js hold the javascript functions.
• docs/generator.css is the style for the generator.

Note that both the js and the css files are loaded via mkdocs.yml.

If you have any questions, please feel free to ping me.
Thank you in advance! 🙏🏻

Are you trying to fix a problem?

No response

Any lead on how this feature can be implemented?

No response

What happened?

By restriction, the package declaration is a reserved key and cannot be used as an actual package name.
i.e. these package names won't work:

• package.com.example
• com.package.example
• com.example.package

The generator should verify this before generating a command.
Currently, we use this simple regex for verifying the package names, this should be modified to include (and reject) the above examples.

Note, we use he same regex variable not only for verifying the package names, but also for verifying the module, and group names, these might need to be segregated.

Please provide runtime information.

Java 18

Relevant log output

No response

How can this issue be reproduced?

• Generate a maven command using the generator using one of the above examples.
• Create the project using the generated command.
• run mvn compile

What happened?

The owner id is used for constructing the scm link, if it contains spaces, it will break.
The current regex matching is not verifying that.

Please provide runtime information.

Not relevant

Relevant log output

No response

How can this issue be reproduced?

No response

What did you have in mind?

Add a reactor archetype variant for creating maven reactor projects.
Implementing this for the 6 currently existing archetypes means that 6 more archetypes are required:

• java-playground-reactor
• java-playground-mod-reactor
• java-advanced-reactor
• java-advanced-mod-reactor
• java-full-reactor
• java-full-mod-reactor

Are you trying to fix a problem?

No response

Any lead on how this feature can be implemented?

No response