maven Original: https://maven.apache.org/guides/mini/guide-naming-conventions.htmlGuide to naming conventions on GroupId, Artifactid and version
- groupId will Identify your project uniquely across all projects, so we need to enforce a naming Schema. It has to follow the package name rules, "what means." is at least as a domain name control, and can Crea Te as many subgroups as you want. Look At more information about the package names.
eg. org.apache.maven , org.apache.commons
A Good The determine the granularity of the groupId is to use the project structure. If the current project is a multiple module project, it should append a new identifier to the parent ' s g Roupid .
eg. org.apache.maven , org.apache.maven.plugins , Org.apache.maven.reporting
- Artifactid is the name of the jar without version. If you created it then you can choose whatever name you want with lowercase letters and no strange symbols. If It's a third party jar, you have the name of the jar as it ' s distributed.
eg. maven, Commons-math
- version If you distribute it so can choose any typical version with numbers and dots (1.0, 1.1, 1.0.1, ...) . Don ' t use dates as they is usually associated with SNAPSHOT (nightly) builds. If It's a third party artifact, you had to use their version number whatever it was, and as strange as it can look.
eg. 2.0, 2.0.1, 1.3.1
GroupId and Artifactid Explained