Skip to content
This repository has been archived by the owner on Apr 7, 2019. It is now read-only.

jodastephen/jpms-module-names

master
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
etc
 
 
 
 
src
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Module names for Java module system

Java SE 9 brought a new feature, the Java Platform Module System (JPMS). Due to certain constraints in the design, it is important for there to be an agreed naming strategy across open source projects. My proposed strategy is detailed here.

In summary, the strategy is:

  • Module names must be valid Java identifiers! E.g. no Java keywords, no dashes, no...
  • Module names must be reverse-DNS, just like package names, e.g. org.joda.time.
  • Modules are a group of packages. As such, the module name must be related to the package names.
  • Module names are strongly recommended to be the same as the name of the super-package.
  • Creating a module with a particular name takes ownership of that package name and everything beneath it.
  • As the owner of that namespace, any sub-packages may be grouped into sub-modules as desired so long as no package is in two modules.

Well-known module names published on Maven Central

To get the whole process started, I've gathered some module names, based on conversations with the relevant projects. Meanwhile, a database of unique module names is ... generated over at sormuras/modules.

Follow-up to sormuras/modules

This project is superseded by https://github.com/sormuras/modules.

About

Module names for the Java Module System (JPMS)

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages