A reasonable group identifier for an individual project?

What is the smart choice of group ID for a maven project that does not fit into any company / organization / website? I understand that the com.companyname.projectname convention is used to avoid namespace conflicts between projects, but how do I come up with a prefix for the individual project I am running?

+4
source share
1 answer

Check out the official guide:

groupId uniquely identifies your project in all projects, so we need to enforce the naming scheme. It must follow the rule package name, which means it should be at least a domain name that you and you can create as many subgroups as you want. look at more information on package names.

eg. org.apache.maven, org.apache.commons

A good way to determine the granularity of groupId is to use the project structure. That is, if the current project is a multiple module, it must add a new parent group identifier identifier.

eg. org.apache.maven, org.apache.maven.plugins, org.apache.maven.reporting

, , , . , . , ", ", . com.andyw.nextbigthing com.nextbigthing. -, , org. org.nextbigthing.

+4

Source: https://habr.com/ru/post/1626911/


All Articles