Maven Archetype should not accept invalid packagenames / create only valid ones

Description

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:

Activity

Show:
Stefan Seifert
January 30, 2018, 2:07 PM

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.

Stefan Seifert
January 31, 2018, 2:03 PM
Alexander Muthmann
January 31, 2018, 2:19 PM

thx, got an error with my wrong package-name

Fixed

Assignee

Alexander Muthmann

Reporter

Alexander Muthmann

Labels

None

Components

Fix versions

Priority

Major
Configure