Repository files navigation

The main goal of this project is to collectUnique Java Modules.As a side product, it also assembles an overview of "almost all" Java modules published at Maven Central since August 2018.

You're welcome to extendThe Watch, becausemodules are coming... and soon the rhyme goes "Modules, Modules, every where!"

Here's the daily updated 🦄modules.properties file of unique modules.

This project considers a Java module to beunique:

• if it is an explicit module with a compiled module descriptor,
• and if its module name that starts with its Maven Group ID or a well-known alias.

Well-known aliases are defined as:

staticStringcomputeMavenGroupAlias(Stringgroup) {returnswitch (group) {case"com.fasterxml.jackson.core" ->"com.fasterxml.jackson";case"com.github.almasb" ->"com.almasb";case"javax.json" ->"java.json";case"net.colesico.framework" ->"colesico.framework";case"org.jetbrains.kotlin" ->"kotlin";case"org.jfxtras" ->"jfxtras";case"org.openjfx" ->"javafx";case"org.ow2.asm" ->"org.objectweb.asm";case"org.projectlombok" ->"lombok";case"org.swimos" ->"swim";default ->group.replace("-","");  };}

Find modulecom.github.sormuras.modules also attached as an executable JAR andToolProvider in the assets ofreleases/tag/0-ea.Stable versions of it are published toreleases; withreleases/latest pointing to the latest stable release.

Thisdoc directory hosts lists of MavenGroup:Artifact coordinates in text files.They are taken as an input of the scan process.Thescanner generates overview tables showing the state of modularization for eachGroup:Artifact coordinate.All JAR files published to Maven Central that were analyzed and recorded by themodulescanner are evaluated using their latest version.That modulescanner was activated in mid of August 2018 - meaning earlier publications can not be evaluated here.

You'll find the following summary at the start of each overview.

• 🧩 denotes a Java module that contains a compiled module descriptor.It therefore provides a stable module name and an explicit modular API usingexports,provides,opens and other directives.

• ⬜ denotes an automatic Java module, with its stable module name derived fromAutomatic-Module-Name manifest entry.Its API is derived from JAR content and therefore maynot be stable.

• ⚪ denotes an automatic Java module, with itsnot stable module name derived from the JAR filename.Its API is derived from JAR content and therefore maynot be stable.

• ➖ denotes an unrelated artifact, like BOM, POM, and other non-JAR packaging types.It also denotes old JAR files, as the scan process can only evaluate artifacts that were deployed after mid August 2018.

    2019 2020 2021 2022 2023🧩  143  163  165  170  171 // Java modules (module descriptor with stable name and API)⬜  205  262  278  310  312 // Automatic Java modules (name derived from JAR manifest)

    2019 2020 2021 2022 2023🧩  155  183  188  196  199 // Java modules (module descriptor with stable name and API)⬜  201  255  270  294  295 // Automatic Java modules (name derived from JAR manifest)

📜Top1000-2023.txt.md

Top1000-2023.txt contains 1,000 MavenGroup:Artifact lines sorted by download popularity of year 2023.

📜Top1000-2022.txt.md

Top1000-2022.txt contains 1,000 MavenGroup:Artifact lines sorted by download popularity as of September 2022.

📜Top1000-2021.txt.md

Top1000-2021.txt contains 1,000 MavenGroup:Artifact lines sorted by download popularity of year 2021.

📜Top1000-2020.txt.md

Top1000-2020.txt contains 1,000 MavenGroup:Artifact lines sorted by download popularity of year 2020.

📜Top1000-2019.txt.md

Top1000-2019.txt contains 1,000 MavenGroup:Artifact lines sorted by download popularity of year 2019.

Find lists of suspicious Maven artifacts in thedoc/suspicious directory.

For example, a Maven artifact is considered to be suspicious if its JAR file contains an illegalAutomatic-Module-Name manifest entry.Illegal? An empty name, a name that contains- characters, a name starting numbers, a name that contains Java keywords, etc., is illegal.Consult chapterModule Declarations of the Java Language Specification for details.TLDR; the name must be usable inrequires NAME; directives of other modules.

Another example is a Maven artifact that contains one or moremodule-info.class files from one or more other Maven artifacts that are already packaged as Java modules.Usually, this is an unwanted side-effect of shad(ow)ing 3rd-party libraries.