On Fri, Feb 14, 2020 at 8:11 AM Hervé BOUTEMY <herve.bout...@free.fr> wrote:
> on that precise case ("commons" instead of "org.apache.commons"), it's
> from
> past Maven 1 repository format time.
>
> then such case is not added to Central for years, only projects that
> existed
> at early Maven 1 repository time (like junit, for example or other
> commons)
> have such names: it's up to each of those veteran projects to choose to
> move
> from their old Maven 1 compliant coordinates to full groupId.
>
> If you know such veteran projects that did not move, just share and tell
> them.
>
>
As "junit" was explicitly mentioned as an example for a vintage (pun
intended)
project here's our reasoning to stick with that very short name ...
forever. At least
for the JUnit 4 (and 3) project artifacts. Including Automatic-Module-Name
attribute introduced in JUnit 4.13:
https://github.com/junit-team/junit4/pull/1571
- junit - Maven Group ID
- junit - Artifact ID
- junit - Java Module Name
JUnit "5", precisely JUnit Platform, Jupiter, and Vintage moved to the
reversed DNS
naming pattern since there day one:
- https://repo.maven.apache.org/maven2/org/junit/platform/
- https://repo.maven.apache.org/maven2/org/junit/jupiter/
- https://repo.maven.apache.org/maven2/org/junit/vintage/
Cheers,
Christian
