Add more validation on the UI field: version

[IvoNet]

Add validation to the version field in the starter UI

'version' should only allow e.g.:

• 1.0.0-SNAPSHOT
• 1.0.0
• 1.0
• 1.2.999-SNAPSHOT
• 1.0.0-RC2

see also here: guide-naming-conventions

Default value should be 1.0.0-SNAPSHOT (as it already is)

[rokon12]

Do we use a regex for this? or use a dropdown of this fixed value.

[rokon12]

Example -

^(?:[1-9]\d*)(?:\.(?:0|[1-9]\d*))*(?:-(?:SNAPSHOT|RC\d+))?$

[m-reza-rahman]

Yes, a regular expression should be good.

[jeyvison]

I'm not sure if we should add a validation for this.

Doing so will force the user to use the pattern we defined instead make it free for them use the version field as they see fit. After all, the naming guide is a convention, not a rule.

[m-reza-rahman]

Agreed. I think this is a very low priority we should look at much later.

[rokon12]

We can mark this one, #150 and #149 as low-priority or remove for now.

[geziefer]

I could do this together with #274

[geziefer]

@m-reza-rahman For clarification: Should the 3 validation tickets apply to UI only or already be incorporated in archetype?
My personal suggestion is to go with UI only, as this is our provided convenient access to the archetype, but if someone uses purely the archetype, he could input whatever he wants as Maven coordinates.

[m-reza-rahman]

I think that’s fine. To be honest I don’t think these validations are super important. They are a nice to have.

[geziefer]

This ticket should be closed as "won't do".
It was already agreed when enhancing the UI that version is not necessarry. It is unlikely, that the user needs to have something different than the default and is able to change this very easy without any effect to other files than the pom.

[m-reza-rahman]

Agreed. Closing for now.