ArtifactId should match module / repo name

Right now there’s microprofile-config but the artifactId for the parent POM is defined as microprofile.config.parent. While dots as separators are quite common especially under Eclipse, see https://github.com/eclipse/rt.equinox.framework, the artifactId should match the module or repository name wherever possible. So either microprofile.config.parent in a repo microprofile.config or an artifactId microprofile-config in the existing name pattern.

[gunnarmorling]

Why using underscores as separator? Hardly ever seeing that out there.

I’d use microprofile-config-1.0.0.Final.jar:

• three digits so we can do bugfix releases like 1.0.1
• an “Alpha”, “Beta”, “CR”, “Final” suffix to have preview releases which can be nicely sorted. That’s the convention we have in Hibernate (and other JBoss) projects and it’s working very well.

[Emily-Jiang]

With my OSGi cap on, as for the bundle version, it has four parts major.minor.micro.qualifier. Since version can be compared, the major, minor and micro follow number comparison while qualifier can be strings, which will follow string comparison (alpha<beta<Final). When we say the number scheme of major.minor.micro.qualifier (microprofile-config-1.0.0.Final.jar), this is the final release. For an alpha release, we have microprofile-config-1.0.0.alpha.jar, which is smaller than microprofile-config-1.0.0.Final. At least, we can differentiate the different stages of the releases.