Using the maven archetype with the following command (which is imho reasonable as Projekt Names can be both uppercase and contain special characters) creates an erroneous package-name:
I'd suspect that the suggested package-name is a valid one but currently this is expected:
this is a problem/bug of the maven archetype plugin - the validation that is defined in the parameter definition is applied when entering the values in interactive mode, not when giving it via command line.
but we can add a custom validation to our post-generation groovy script to at least fail with a sensible error message after the generation.
thx, got an error with my wrong package-name